Gentoo Archives: gentoo-dev

From: Bjarke Istrup Pedersen <gurligebis@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] eselect modules
Date: Sun, 04 Sep 2005 18:27:52
Message-Id: 431B3B7E.1080609@gentoo.org
In Reply to: [gentoo-dev] eselect modules by Jeremy Huddleston
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Jeremy Huddleston skrev:
5 > I've recently updated opengl-update to use the eselect framework. I
6 > think the team has done a great job as it was extremely easy to port the
7 > bash script to an eselect module. However, when I placed it in the
8 > portage tree, it sparked a little bit of a policy discussion between
9 > myself and the core eselect devs on how to best include modules in the
10 > tree, so I'd like to let other devs chime in as well.
11 >
12 > Firstly if you don't know what eselect is, check out:
13 > http://www.gentoo.org/proj/en/eselect/index.xml
14 >
15 > The eselect developers want to keep all eselect modules in their svn
16 > repository and distributed through a single package (app-admin/eselect).
17 > Their main reasons for this are better QA and less overhead for releases
18 > and merging.
19 >
20 > I have a problem with this policy because:
21 > 1) Stability of the modules should not be tied to stability of the core
22 > package. Basically, I'd like to determine when my modules get pushed
23 > into stable without considering how it'll effect the eselect modules of
24 > other developers. Similarly, I don't want bugs in another module
25 > holding up my module from going into stable.
26 >
27 > 2) Not all users will want all modules. The goal of the eselect project
28 > is to provide a framework to replace java-config, motif-config,
29 > gcc-config, binutils-config, opengl-update, etc, but not all users will
30 > need all modules.
31 >
32 > 3) Some modules require extra files (opengl-update installs header
33 > files, gcc-config installs a wrapper, etc), and the app-admin/eselect
34 > package is not the correct place to provide these files.
35 >
36 > Also, what should the correct way to introduce these modules into
37 > portage?
38 > Should we keep them in the packages they're replacing
39 > (x11-base/opengl-update)?
40 > Should we place them in a new package in the same category as the script
41 > they're replacing (x11-base/eselect-opengl)?
42 > Should we place them in app-admin/eselect-<module name> or perhaps
43 > app-eselect/<module name>?
44 >
45 > Note that for backwards compatibility in all cases,
46 > x11-base/opengl-update will RDEPEND on this eselect module and install a
47 > backwards-compatible frontend to the eselect module until all packages
48 > in portage have been updated to use the eselect module instead.
49 >
50
51 Any plans on moving webapp-config as an eselect module? :-)
52 -----BEGIN PGP SIGNATURE-----
53 Version: GnuPG v1.4.2 (MingW32)
54 Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
55
56 iD8DBQFDGzt+O+Ewtpi9rLERAiZgAKDAzrI29bEbUoVKdji4r9vaZOFFcwCdGbfo
57 rXlfU7yQb6qvpuMj2BR806Y=
58 =d86l
59 -----END PGP SIGNATURE-----
60 --
61 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] eselect modules Stuart Herbert <stuart@g.o>
Re: [gentoo-dev] eselect modules Ciaran McCreesh <ciaranm@g.o>