On Wednesday 09 May 2007 6:39:41 am Essien Ita Essien wrote:
> Strip ArchLinux down to a small tight Core that does one thing ONLY
> ====================================================================
>
> I think we have *too* many packages in current and extra. I think we
> ought to rethink the basics of Arch and look at it in the light of our
> current scenario.
<snip snip>
>
> [gui-core] : users of this project, would have the _extreme_ minimal
> stuff neccessary to get a gui system up and running. This would not have
> any Window Manager specific packages, just the basic core, like Xorg,
> dbus, hal, etc, - This one is goad oriented, and if careful design,
> should be small enough to be also probably managed by the core team.
>
> [daemons]
> This would be a category oriented project, that would be a catch all for
> various contributed packages. postfix, sendmail, mail, mysql, postgres,
> etc... all come in here. if over time, a group of ppl are highly
> specialized on say mail or even specifically qmail, they can extract
> themselves and their packages from [daemons] and start a [qmail] or
> [mail] project. This wouldn't be under the care of the core team.
>
> [network-utils]
> category for stuff like tcpdump, netcat, hping, ntop, etc.
>
> [development] : a category repo for various language compilers,
> intepreters, etc... and then there would definitely be a need for
> specialized groups like [python], [perl], [ruby], these would not be
> under the care of the core team.
>
> [webframeworks]: need not be said, django, RoR, turbogears, cakephp,
> codeigniter, you name it. And if some one starts a [django] well, enjoy.
>
> [gnome], [kde], [e17], [matchbox], etc would also exist here, maintained
> by their various fanatic^H^H^H^H^Hs
>
> It should be noted that these repositories/projects would have
> dependencies on others. for instance [gui-core] would need [base] and
> any of [kde], [gnome], etc, would need [gui-core]
This might sound awesome at first, but inter-dependency between packages in
different repos could end up being a really big nuisance!
Actually, I'd suggest merging current and extra if possible.
The categorization that you mention is already done in the cvs repo layout
(look at all the folders in the cvs tree).
Also, pacman could have an optional feature for 'labels' ('tags' in web2.0
language) if really needed.
--
Vinay S Shastry
_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch
