-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks Does anyone happen to know (and I hope a few packagers @SUSE are reading this list ;)) if there's some kind of policy for SUSE's supplementary repositories ? I mean, I might be wrong but I have the feeling that sometimes, new stuff gets packaged and included there but... - - not everything (which isn't a problem, work for us community packagers) - - sometimes with a delay of several days or even weeks after the released The 2nd point is quite annoying for us community packagers (well at least it is for me), as sometimes we do package newest versions (as SUSE only provides backported security fixes) and then a few days (or sometimes 1-2 weeks) later, it shows up in KDE or GNOME supplementary. It's nice and all, but if someone working @SUSE tells me he's maintaining things like amarok or k3b and always keeps up with the latest releases, I don't see the point in me having a few hours of work to package them as well (except maybe providing them for SUSE versions that are not in supplementary) ;) The question is: do you (SUSE devs) always keep up with the latest versions of applications that are in supplementary ? Or is it "when we have the time" ? I can imagine it has low priority.. 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) iD8DBQFDf8A+r3NMWliFcXcRAtGKAKCyZddQatLdS6Q92gZGwtUkqTgfkgCgg0t0 DGwL64TGYNhrUN4XMPBSLDw= =+cpf -----END PGP SIGNATURE-----