From: Alec Joseph Warner <warnera6@egr.msu.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Questions about CVS locations and GID...
Date: Wed, 05 Oct 2005 16:25:37 -0400 [thread overview]
Message-ID: <434436C1.2050305@egr.msu.edu> (raw)
In-Reply-To: <e36b84ee0510051318s5ab51072k663d78c35dbed25f@mail.gmail.com>
m h wrote:
> Sorry, on further reading of my post, my questions weren't clear. My
> first question is where is the current head of portage in CVS? (I'd
> like to compare with what I have, and I'm not sure if I'm looking in
> the right place).
>
> WRT implementing Prefix. I'm looking at Michael's code, because I
> want to see what he has done. (Which seems to be inline with what I
> need, may or may not align with the gentoo community at large, since
> nothing has been decided on that front).
>
> Though, I noticed there was mention of Prefixed installs in yesterdays
> GWN (http://www.gentoo.org/proj/en/gentoo-alt/). If anyone can
> elaborate on the efforts going on in that arena, I'm all ears.
>
> matt
>
> On 10/5/05, Alec Joseph Warner <warnera6@egr.msu.edu> wrote:
>
>>
>>m h wrote:
>>
>>>Hey Folks-
>>>
>>>I'm working on trying to get prefixed installs working. (As such, I'm
>>>using some code kindly modified by Michael Haubenwallner. ) I'm now
>>>in python code (portage) and would like to compare what I have with
>>>gentoo proper.
>>>Is this the location of the latest up to date portage code (in CVS, I
>>>realized devs might have more "up to date" code on their boxes):
>>>http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/pym/?root=gentoo-src
>>>
>>>I looked through the dev documentation but couldn't find anywhere
>>>where it stated the actual location of the code in CVS. Any pointers
>>>would be great.
>>>
>>>thanks,
>>>matt
>>>
>>>ps.
>>>The issue I found is with pym/cache/fs_template.py. If I'm running as
>>>root (GID = 0) then this fails:
>>>
>>> def __init__(self, label, auxdbkeys, basepath=None, gid=-1,
>>>perms=0664, **config):
>>> """throws InitializationError if needs args aren't specified"""
>>> if not gid:
>>> raise
>>>cache_errors.InitializationError(self.__class__, "must specify gid!")
>>>
>>>Shouldn't the logic be "if gid != -1"? I don't have access to a
>>>gentoo proper box right now...
>>>
>>
>>I thought that part of brian's domain stuff in Savior was to cover this.
>> In either case no one should be writing any real code at this point
>>since no one has agreed on any sane way to pull this off. There needs
>>to be plenty of healthy discussion the pro's and con's of how things
>>should be done in regards to *-prefix.
>>
>>In conclusion, if you think this will be 'easy', think again ;)
>>
>>PS. However starting discussion on how exactly this would work might be
>>a nice thing to do ;)
>>--
>>gentoo-portage-dev@gentoo.org mailing list
>>
>>
>
>
* Now talking on #gentoo-portage
* Topic for #gentoo-portage is: 2.0.53_rc3 released; please test ||
emerge development only; ebuild dev questions go to #gentoo-dev-help and
usage questions go to #gentoo || anonsvn access: svn co
svn://twobit.net/portage/, rewrite is at main/branches/savior, 2.1 is at
main/trunk, 2.0 is at main/branches/2.0 and sandbox is at path-sandbox/trunk
IRC is your friend here ;) In this case you probably want the rewrite,
which is from what I recall, a complete rewrite...so nothing of Haubi's
is in it. Brian will definately know more there than myself, I haven't
touched it in quite some time, and I doubt RL will let me for a bit :P
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-05 20:26 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 18:35 [gentoo-portage-dev] Questions about CVS locations and GID m h
2005-10-05 19:54 ` Ciaran McCreesh
2005-10-05 20:06 ` Alec Joseph Warner
2005-10-05 20:18 ` m h
2005-10-05 20:25 ` Alec Joseph Warner [this message]
2005-10-05 20:24 ` Brian Harring
2005-10-05 20:48 ` m h
2005-10-05 21:10 ` Brian Harring
2005-10-05 21:52 ` m h
2005-10-05 22:02 ` Brian Harring
2005-10-05 23:01 ` m h
2005-10-05 23:10 ` Brian Harring
2005-10-05 20:57 ` Ciaran McCreesh
2005-10-05 21:13 ` Brian Harring
2005-10-05 22:31 ` Ciaran McCreesh
2005-10-05 23:00 ` Brian Harring
2005-10-05 23:14 ` Ciaran McCreesh
2005-10-05 23:22 ` Brian Harring
2005-10-05 23:38 ` Ciaran McCreesh
2005-10-05 23:40 ` Brian Harring
2005-10-06 0:13 ` Ciaran McCreesh
2005-10-06 1:01 ` Brian Harring
2005-10-06 1:07 ` Ciaran McCreesh
2005-10-06 1:17 ` Brian Harring
2005-10-06 1:23 ` Ciaran McCreesh
2005-10-06 1:32 ` Brian Harring
2005-10-06 1:40 ` Ciaran McCreesh
2005-10-06 1:48 ` Brian Harring
2005-10-06 2:01 ` Ciaran McCreesh
2005-10-06 2:39 ` Brian Harring
2005-10-06 11:51 ` Ciaran McCreesh
2005-10-06 12:08 ` Jason Stubbs
2005-10-06 13:07 ` Alec Warner
2005-10-06 18:29 ` Ciaran McCreesh
2005-10-06 18:42 ` Brian Harring
2005-10-06 19:11 ` Ciaran McCreesh
2005-10-06 1:56 ` Kito
2005-10-06 2:02 ` Ciaran McCreesh
2005-10-06 2:11 ` Kito
2005-10-05 23:27 ` Alec Warner
2005-10-05 23:38 ` m h
2005-10-05 23:46 ` Alec Warner
2005-10-05 21:16 ` Kito
2005-10-05 21:34 ` Brian Harring
2005-10-05 22:29 ` Ciaran McCreesh
2005-10-05 22:53 ` Brian Harring
2005-10-05 23:03 ` Ciaran McCreesh
2005-10-05 23:21 ` Brian Harring
2005-10-06 4:14 ` Finn Thain
2005-10-06 4:22 ` Brian Harring
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=434436C1.2050305@egr.msu.edu \
--to=warnera6@egr.msu.edu \
--cc=gentoo-portage-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