-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 houghi wrote:
On Mon, Sep 19, 2005 at 12:01:30AM +0200, Eberhard Moenkeberg wrote: ... Great. As you know something that is installed via a non-official repo will become locked. This causes it to be excluded from newer versions, wich might be importand in case of security patches. Would this also be handled?
That needs to be adressed by the YaST2 developers. If you use apt or redcarpet, those packages are not "locked", and they may not be. It's a broken approach.
Say I compile a packagage and after two weeks a newer version comes out due to security reasons, will users who installed the first package get the newer version?
With YaST2, I don't know. It might be "locked" and you wont get the latest package. With apt, yum or redcarpet you'll simply end up with the package that's the "highest" in its naming scheme. That isn't always working as expected either, which is why we (packagers) need to communicate and coordinate to avoid duplicated RPMs (in different repositories). But you got the point, you've scratched the tip of the iceberg ;) Still a lot to do. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDLmVjr3NMWliFcXcRAh+dAJ9GwiLzVCyQRwcFBn8EHI2vilkKVgCfTHfb ZrDkfj5G2Y6LLOXWiMxk1y4= =5xcx -----END PGP SIGNATURE-----