Re: [rock-user] updating/upgrading... policy
Pupeno <[email protected]>
| Newsgroups | gmane.linux.distributions.rock.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 22 April 2004 19:02, Alejandro Mery wrote: > as you said, it is not possible to have an official ROCKLinux binary > repository because there is no ROCKLinux distribution ;) what there can Can't there be an official Rock Linux distribution ? even when Rock Linux is a distribution building kit, having something like the base, something like gentoo's GRP or something like that. > ROCK is a distribution build kit, and not a distribution, then someone > like you can use it to design, and maintain your own ROCK-based > distribution, with your own repository of built stuff for the different > architectures you choose to support. Ok, I might have the repository... then, how do the users of my distro upgrade to my repository ? Since there doesn't seem to be a tool to upgrading binary packages like apt... should this tool be developed by the subdistro developers or is it something that would be welcome in main Rock ? > what you should have in mind is that .gem files are $package-$ver.gem > and not $package-$ver-$build as redhat and other does, then small > changes not reflected in the version of the package will not create a > new filename. of course the date will be newer. Oh, that is a problem because it is something very common to solve bugs in the packages and upgrade. How can that be solved ? Can the name be created like in redhat ? or do you think it'd be possible to make an upgrade tool that would use dates to upgrade ? Thanks. - -- Pupeno: [email protected] http://www.pupeno.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAiHqQtCepaMf3unIRAl2PAJ9GQiv73mQfEF6HG2DPygIiHkn7hgCgg/zl O6agHFgAiN7kxE8BJvmOr9A= =1+Sj -----END PGP SIGNATURE-----