-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston skrev:
I've recently updated opengl-update to use the eselect framework. I
think the team has done a great job as it was extremely easy to port the
bash script to an eselect module. However, when I placed it in the
portage
Jeremy Huddleston wrote:
I've recently updated opengl-update to use the eselect framework. I
think the team has done a great job as it was extremely easy to port the
bash script to an eselect module. However, when I placed it in the
portage tree, it sparked a little bit of a policy discussion
I've recently updated opengl-update to use the eselect framework. I
think the team has done a great job as it was extremely easy to port the
bash script to an eselect module. However, when I placed it in the
portage tree, it sparked a little bit of a policy discussion between
myself and the core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston wrote:
| The eselect developers want to keep all eselect modules in their svn
| repository and distributed through a single package (app-admin/eselect).
| Their main reasons for this are better QA and less overhead for releases
|
On Tue, 2005-08-16 at 12:21 -0700, Donnie Berkholz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston wrote:
| The eselect developers want to keep all eselect modules in their svn
| repository and distributed through a single package (app-admin/eselect).
| Their main
On Tue, 16 Aug 2005 15:38:08 -0400 Chris Gianelloni
[EMAIL PROTECTED] wrote:
| There's also the size issue. I use opengl-update on the LiveCD
| builds, and have exactly zero need for *any* other eselect module, so
| why should I be required to have them all to just get the one that I
| need?
On Tue, 16 Aug 2005 21:52:25 +0200 Danny van Dyk [EMAIL PROTECTED]
wrote:
| b) The possibility to change all modules in one move in case we change
| ~ something like a default behaviour, or function names, etc.
That kind of thing shouldn't happen once a stable release is out...
--
Ciaran
