Re: [gentoo-dev] RFC: Last rites for $package ...
Or you haven't talked to me or Beandog at all; since he has been working on this a while (now with upgraded tools!). what i'd like to see is a system, to which one would give a package name, which then handles the removal (almost) automatically. that way devs would have an easier time actually removing some cruft and you guys would be freed from typing the same stuff over and over. this system could be responsible for sending the out last rites mails, masking the packages in package.mask etc... enrico would get his database for free, both listing those that are pending removal as well as a history of removals including the reason plus a pointer to the corresponding bug... don't know if that is what you are aiming at, but currently the process of removing a package is a true chore and i admire your dedication to it. (a big THANKS btw) regards bangert pgpF8znVcu4fw.pgp Description: PGP signature
[gentoo-dev] RFC: Last rites for $package ...
Hi folks, maybe you remember the discussion about package removal and problems for users on that ... The problem was: someone (who's not reading this list) might be interested in some package (or even had installed it) and now gets trouble because its (from his view) sudden removal. An solution could be an database of packages scheduled for removal. But this database has to be maintained. And it doesn't seem that there's someone who's interested in doing this extra work. As I've seen talks about such removals seem to happen under the suject Last rites for $package, I'm now going to set up an little mail robot, which catches those mails and adds the named package to an removal-scheduled-database. To make this working realiably, we simply need to agree on one thing: : If an package is going to be removed, there *always* has to be : an discussion w/ subject Last rites for $package : (where $package is the qualified package / port name) Maybe we could also define other some other subject for the cases that removal is aborted or committed. What do you think about that ? cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: Last rites for $package ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: Hi folks, snip To be perfectly honest, we're not going to hold someone's hand with this. We shouldn't be expected to. A package will be in mask for a month before its removed. That's a good warning sign that something is up. You can view the package mask file and see the reason behind it, as well you have this mailing list where announcements about what is masked and when its removed. If people can't find the reason from all those sources of data..then quite frankly..there's a larger issue going on with them. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFHDUySENan+PfizARAk/eAJ4jHTvqjjWBHFSgY24Wkb3XTits3QCfVgUz JOj/wWgWBaCVxVyfeh23PKM= =1IPj -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: Last rites for $package ...
On Thu, 28 Sep 2006 22:28:27 +0200 Enrico Weigelt [EMAIL PROTECTED] wrote: An solution could be an database of packages scheduled for removal. But this database has to be maintained. And it doesn't seem that there's someone who's interested in doing this extra work. As I understand it, every one of these package removals is first package.masked for 30 days before the ebuilds are actually removed. So, the user has a month in which to do something about this. When they sync and try to update any time during that month, they will see a message, telling them that that package is scheduled for removal, and pointing them at the relevant bugs in bugzilla. So, isn't package.mask already that database? Or am I missing something? -- Mike Kelly -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: Last rites for $package ...
Enrico Weigelt wrote: An solution could be an database of packages scheduled for removal. But this database has to be maintained. And it doesn't seem that there's someone who's interested in doing this extra work. Well, there is bugzilla. Just track any bugs with [EMAIL PROTECTED] in there and you'll see what were up to. Steve -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: Last rites for $package ...
The problem was: someone (who's not reading this list) might be interested in some package (or even had installed it) and now gets trouble because its (from his view) sudden removal. My project is responsible for what I'd imagine to be the most tree removals; we have strict guidelines regarding packages. For instance; the package must have a bug filed against it; it gets masked for 30 days prior to being actually punted; you should always see e-mail on this list regarding both it's masking and removal...These are all things to ensure people are aware of what is going on; this is not some hidden process. An solution could be an database of packages scheduled for removal. But this database has to be maintained. And it doesn't seem that there's someone who's interested in doing this extra work. Or you haven't talked to me or Beandog at all; since he has been working on this a while (now with upgraded tools!). There has been a GPNL description on the Treecleaner project page since day one; since *I* wrote it. Yeah it's not up yet; yeah I'm removing packages anyway; hopefully with the GPNL it will be more obvious to some people; but then you still need to search GPNL to see what the heck is scheduled for removal. Frankly if you can't read the ML archives or search on bugs when a package you find is masked; then I don't really know where else to point you... -Alec Warner TreeCleaners Lead -- gentoo-dev@gentoo.org mailing list
