From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Moving some packages around
Date: Mon, 12 May 2008 02:58:55 +0200 [thread overview]
Message-ID: <m2k5i0jq28.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2313 bytes --]
I've been thinking today that we have a lot of things in sys-devel that
shouldn't probably be there, like pmake and bmake.
I'd propose the following move, if nobody has arguments aginst those:
sys-devel/bmake -> dev-util/bmake
sys-devel/pmake -> dev-util/pmake
sys-devel/bison -> dev-util/bison
sys-devel/flex -> dev-util/flex
sys-devel/autoconf-archive -> dev-util/autoconf-archive
sys-devel/ac-archive -> dev-util/ac-archive
sys-devel/cons -> dev-util/cons
sys-devel/gdb -> dev-util/gdb
sys-devel/omni -> dev-lang/omni
Reasoning for the moves:
- bmake and pmake are additional make commands from the basic one,
G/*BSD will have their own in -ubin or -bin, while the rest of the
system uses GNU make as sys-devel/make;
- bison and flex should get out of the system package set, what clearer
than moving them out of sys-*? They are not so commonly used so there
should no compelling reason to have them installed on every system;
- autoconf-archive and ac-archive are not really something for your
system;
- cons is not commonly used as build system, so should probably be
together with the other not-so-used build systems;
- gdb is not part of the system, this might be a problem for
crossdev...;
- omni is ... well not something I'd look for in sys; plus it's a
compiler so it would probably suite dev-lang better.
There are a few I'm not sure of because I don't know the package at all,
or because I have mixed feelings about them:
sys-devel/remake -> dev-util/remake
sys-devel/sparse -> dev-util/sparse
sys-devel/distcc -> dev-util/distcc
sys-devel/icecream -> dev-util/icecream
sys-devel/m4 -> dev-lang/m4
sys-devel/patch -> app-text/patch
sys-devel/prelink -> sys-apps/prelink (something else? It's not a devel
package...)
sys-devel/autogen -> dev-util/autogen
sys-devel/dev86 -> dev-lang/dev86
sys-devel/bin86 -> dev-lang/bin86
sys-devel/gettext -> app-i18n/gettext (well, it's part of system for
G/FBSD, but I'd rather have deps expressed properly...)
Yes these are a lot of moves, sincerely I think sys-* categories are a
bit bloated as they are, and I suppose we should start moving the things
around rather than waiting forever ad ever..
--
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next reply other threads:[~2008-05-12 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 0:58 Diego 'Flameeyes' Pettenò [this message]
2008-05-12 1:46 ` [gentoo-dev] Re: Moving some packages around Ryan Hill
2008-05-12 2:08 ` Ryan Hill
2008-05-17 23:15 ` Ulrich Mueller
2008-05-18 13:28 ` Diego 'Flameeyes' Pettenò
2008-05-18 14:50 ` Ulrich Mueller
2008-05-12 2:30 ` [gentoo-dev] " Marius Mauch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k5i0jq28.fsf@gmail.com \
--to=flameeyes@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox