[arch-dev-public] Package cleanup - implementation

Dan McGee dpmcgee at gmail.com
Fri May 11 18:29:29 EDT 2007

On 5/11/07, Thomas Bächler <thomas at archlinux.org> wrote:
> Aaron Griffin schrieb:
> > This is a note for the developers.  If you haven't seen the busy
> > thread on the general list regarding package cleanup, this wiki page
> > should cover everything:
> >
> > http://wiki.archlinux.org/index.php/Package_Cleanup
> >
> > Before the end of the weekend, I'm going to move most of these
> > packages based on what is there.  There are a few that are
> > questionable, however, so please voice you opinions if you don't want
> > things touched.
> - I don't know why we would move i18n stuff out of extra. The "default
> is english, would take a lot of load away" seems arrogant, at best.

The issue here is shifting the maintenance away from the devs to a set
of TUs, not dropping i18n support from Arch Linux. Let me point out a
few pros and cons.

1. More maintainers = more testing and frequent updates. Instead of
only allowing devs to update the localizations, we allow TUs to do
this as well. Devs should have no problem still doing this as well-
they should be able to update anything in community if necessary.
2. It separates the building tasks (package and l10n), allowing the
developer to focus more on the package and others on the
localizations. This would hopefully encourage developers to do better
3. ?

1. People may frown a bit upon 'community' taking a more official
role, although I think this perception should be changed.
2. ?

Fill in the blanks if you got reasons.


More information about the arch-dev-public mailing list