[arch-dev-public] Next package cleanup [was next major steps have to be planned]
belanger at ASTRO.UMontreal.CA
Thu Sep 20 21:31:21 EDT 2007
On Thu, 20 Sep 2007, Aaron Griffin wrote:
> On 9/20/07, Eric Belanger <belanger at astro.umontreal.ca> wrote:
>>> 4) So we need to revisit, once again, the package cleanup that I had
>>> started months ago. Eric, you were helpful last time - would you be ok
>>> with figuring out the details of another round of cleanup?
>> Sure. I already have a few names in my mind because a while ago I tried
>> porting packages to x86_64 and came across several ones where the sources
>> were missing or that were dead projects. I'll also check again the wiki
>> list and the orphaned packages in the repo.
>> Before removing anything, I'll post the list of candidates for removal
>> here with a short reason for the removal to inform you and give an
>> occasion to contest the removal of a package.
> Great, thanks a lot! The last time, we had a lot of success with a
> public wiki and getting the userbase involved. Do you think that's
> still appropriate until we winnow the packages to a more concrete set?
> Or should we stick to internal at this time and get rid of packages
> with incompatibilities and the like?
> -- Aaron
Most of that wiki page was about moving current packages to extra which
was done when we did the core repo. I think we can do the cleanup
internally. If we are unsure about a few packages, we can always ask the
users at that time.
To begin the cleanup, everyone should go through his package set and
orphan any packages they don't have interest/time in maintaining. Also,
check the orphaned packages for packages that you'll want to maintain.
This will help in spreading out the workload and make sure all
owned packages have an interested maintainer.
When going through your packages, look for any potential candidate, i.e.,
dead projects (packages whose last update was several years ago) or
packages were better, more modern alternatives exists.
I've setup a list on the dev wiki:
so that everyone can add to the list.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the arch-dev-public