public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: m h <sesquile@gmail.com>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Re: Attempt to use prefix on linux as secondary...
Date: Fri, 16 Dec 2005 11:39:11 -0800	[thread overview]
Message-ID: <e36b84ee0512161139m7ea6ed02hd27d2329aa8b304c@mail.gmail.com> (raw)
In-Reply-To: <20051216122010.GG30053@nightcrawler.e-centre.net>

On 12/16/05, Brian Harring <ferringb@gentoo.org> 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...

>
>

-- 
gentoo-osx@gentoo.org mailing list



  reply	other threads:[~2005-12-16 19:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 23:21 [gentoo-osx] Attempt to use prefix on linux as secondary m h
2005-12-14 23:27 ` Nathan
2005-12-15  1:03   ` m h
2005-12-15  1:48     ` m h
2005-12-15  2:34       ` Kito
2005-12-15  6:17         ` m h
2005-12-15  6:35           ` Kito
2005-12-15  2:34 ` Kito
2005-12-15  7:31 ` Grobian
     [not found] ` <1134637115.30023.36.camel@sapc154>
2005-12-15 19:15   ` [gentoo-osx] " m h
2005-12-15 23:27     ` m h
2005-12-16  0:35       ` m h
2005-12-16  0:59         ` m h
2005-12-16  1:51           ` m h
2005-12-16 12:18             ` Brian Harring
2005-12-16 19:10               ` m h
2005-12-16 12:26           ` Brian Harring
2005-12-16 12:34             ` Brian Harring
2005-12-16  5:19         ` Nathan
2005-12-16 12:10           ` Grobian
2005-12-16 12:13         ` Grobian
2005-12-16 12:19           ` Grobian
2005-12-16 19:13             ` m h
2005-12-16 19:12           ` m h
2005-12-16 12:20         ` Brian Harring
2005-12-16 19:39           ` m h [this message]
2005-12-16 19:48             ` m h
2005-12-17 13:49 ` [gentoo-osx] " Grobian
2005-12-17 14:27   ` Grobian
2005-12-17 16:37     ` m h
2005-12-17 16:48   ` m h
2005-12-17 18:25     ` Grobian

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=e36b84ee0512161139m7ea6ed02hd27d2329aa8b304c@mail.gmail.com \
    --to=sesquile@gmail.com \
    --cc=gentoo-osx@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