On 12/16/05, Brian Harring <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 15, 2005 at 04:35:36PM -0800, m h wrote:
> > Got around (hacked around) python issue (I have no portage user
> > currently, only the group). So in portage_data.py, I override
> > portage_uid to my userid
> > portage_uid=os.getuid()
> > and I'm rolling again.
> ./configure --help | less # instead
> there's configurable's for defining uid/gid. Down the line (repeating
> myself), if this is mainlined, proper implementation will be created
> where config can define/adjust uid/gid's to use instead of current
> hardcoding at install time.
> ~harring
>
it looks like Haubi's toolbox is doing the right thing here (setting
the right configure flags):
src_build() {
echo "ENV:"
env
echo "MATT"
configureflags=
case "${PLATFORM}" in
SunOS)
XCU_ID=/usr/xpg4/bin/id
;;
*)
XCU_ID=/usr/bin/id
;;
esac
if [ -x "${DESTDIR}/bin/bash" ]
then
CU_BASH="${DESTDIR}/bin/bash" export CU_BASH
fi
configureflags="${configureflags} --with-offset-prefix=${DESTROOT}"
configureflags="${configureflags} --prefix=${DESTROOT}/usr"
configureflags="${configureflags} --with-user=`${XCU_ID} -un`"
configureflags="${configureflags} --with-rootuser=`${XCU_ID} -un`"
configureflags="${configureflags} --with-group=`${XCU_ID} -gn`"
configureflags="${configureflags} --with-wheelgroup=`${XCU_ID} -gn`"
gnu_build || die
}
Even if these are set, there is some hardcoded values in portage....
No biggie. Just need to edit them...
>
>
--
[email protected] mailing list
