[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Moving functionality out of portage and into the tree
From:       Brian Harring <ferringb () gentoo ! org>
Date:       2004-07-31 4:45:30
Message-ID: 7345730A-E2AC-11D8-A39E-000A95C08860 () gentoo ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jul 30, 2004, at 10:15 AM, Jason Stubbs wrote:

> On Friday 30 July 2004 09:53, Brian Harring wrote:
>> For commentary above, I've assumed you're talking about bash
>> functionality- if you're referring to the scripts in bin/*, we've yet
>> to bundle those w/ an installed ebuild.  Possible I spose, although
>> again, that falls under another thread/bug; it would be an extension 
>> of
>> portage's env snapshot code, and wouldn't care about where it got the
>> scripts from, just as long as it could find them :)
>
> I assumed that, with the moving of most of bin/*, everything would go 
> into one
> (or more) eclass(es). At least, that seems the most convenient way to 
> me.

Viable for the bash based scripts, although my original plan had been 
just to move them into the tree in their current form.
Changes down the line to how they are stored, eg- if they are kept as 
they are, if they are stored in one giant script, if we have them 
source as actual bash functions, etc, is a bit dependant on if the env  
saving/restoring mechanisms are cleaned up.  Until ebuild.sh correctly 
preserves the env's attributes, and stop's overwriting portions of it 
by default, I'd prefer to keep the scripts as they are.
Besides, the move is the big thing.  With that out of the way, it's 
upto the new herd to determine how it's arranged/handled (within limits 
of course).

>  Do
> you have a fairly clear view in mind of exactly what would stay and 
> what
> would be moved yet?
For scripts, everything.
For bash functions, that's a bit trickier.  Note, we don't have to move 
*everything* in a giant exodus, things can be shifted out down the 
line.
That said, these come to mind.

econf, emake, einstall, einfo, ewarn,
use, usev, use_enable, use_with,
pkg_pre*, pkg_post*, pkg_fetch, pkg_nofetch,
src_unpack, src_compile, src_install, src_test,
has, hasv,
enable_qa_interceptors, disable_qa_interceptors,
*opts functions,
*into functions,

That should *roughly* cover it.  Once carpaski speaks up on this 
(yay/nay), I can go through and build a final list.
~brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBCyPtvdBxRoA3VU0RAq/7AKCvoghoFMtFwQQrIYzS2XZFw4vSSQCggkzA
32pKiEvcZLTcTESWBVijCaw=
=s8hS
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]