From: Greg W. <pqt...@sn...> - 2001-05-16 09:28:17
|
*********** REPLY SEPARATOR *********** On 13/05/2001 at 8:47 PM Jamie Cameron wrote: >Greg Wright wrote: >> >> Hello Jamie, All, >> >> I have been meaning to ask this/look for some time. >> >> As updates are done to modules after a release, are these new modules >> included in the download package & RPMs, or is it required to do the >> updates manually (I guess the later). > >The latter - the 0.85 RPM stays constant after it is released. >Technically, there is no reason why I couldn't put out a new partial >version (like 0.851) for each update, but is that what other open-source >projects usually do? Gee, I see so many messages about this, it was not meant to spark this, I just wanted to know where things stand. As far as having a daily snapshot, I do not see the need for that as we know what we are dealing with most of the time, ie we have Perl scripts to control specific services, however, it would be good to be able to get a hold of a tarball that has the updated modules included, this would also allow the creation of updated RPMs pretty easily by just replacing the tarball in the SRPM package with the latest before re building. I do not see any advantage to the user & especially to you to have to create sub releases. I guess I could also just create my own tarball and save you any hassle, my message was not meant to imply "will or would you do this". Regards Greg Wright -- IT Consultant Sydney Australia PH 0418 292020 Available for Global Contracts Int. +61 418 292020 Web http://www.ausit.com E-mail Greg AT AusIT.com Trading As - AAA Computers -- providers of IT services. |