Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 82312 - Darwin userland patch
Summary: Darwin userland patch
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2005-02-16 22:51 UTC by Kito (RETIRED)
Modified: 2005-07-14 06:58 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Patch to add USERLAND="Darwin" (portage-2.0.51.16-darwin.patch,4.13 KB, patch)
2005-02-16 22:52 UTC, Kito (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kito (RETIRED) gentoo-dev 2005-02-16 22:51:04 UTC
adds separate userland for the Darwins.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Kito (RETIRED) gentoo-dev 2005-02-16 22:52:00 UTC
Created attachment 51402 [details, diff]
Patch to add USERLAND="Darwin"
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2005-02-17 04:02:44 UTC
I'm pretty sure this patch will kill support on BSD. Could you please come to some agreement on how chflags will be handled? How gsed and friends will be handled? Any other issues..? Thanks :)
Comment 3 Kito (RETIRED) gentoo-dev 2005-02-19 10:53:29 UTC
*bsd folks, anyword on this? This is bordering on being a blocker for us as all .a files are h0rked, thus preventing even gcc from being merged.
Comment 4 Stephen Bennett (RETIRED) gentoo-dev 2005-02-19 11:04:11 UTC
I've been using the above patch on fbsd for a couple of days, and it doesn't seem to have broken anything yet...
Comment 5 Jason Stubbs (RETIRED) gentoo-dev 2005-02-20 01:45:21 UTC
I looked again and I don't see any wrong either. ;)

I misread the following from etc-update:

 if [ $(/usr/lib/portage/bin/portageq envvar USERLAND) = BSD ] ; then
 	function sed() { gsed "$@"; }
+elif [ $(/usr/lib/portage/bin/portageq envvar USERLAND) = Darwin -a -x /bin/gsed ]; then
+	function sed() { gsed "$@"; }

as the added blocks replacing the original blocks. Should probably make it something like the following anyway though:

-if [ $(/usr/lib/portage/bin/portageq envvar USERLAND) = BSD ] ; then
+USERLAND="$(/usr/lib/portage/bin/portageq envvar USERLAND)"
+if [ "$USERLAND" == "BSD" ] || [ "$USERLAND" == "Darwin" ] ; then
 	function sed() { gsed "$@"; }

That makes it consistent with the rest of the code, prevents a second call to portageq on most OS's and saves a line of code. :)
Comment 6 Kito (RETIRED) gentoo-dev 2005-02-20 11:00:09 UTC
Ahh, thank you sir, less lines is always most bestest =)

I did want to check that gsed exists and is executable, as some systems have GNU sed installed without the g prefix.

-if [ $(/usr/lib/portage/bin/portageq envvar USERLAND) = BSD ] ; then
+USERLAND="$(/usr/lib/portage/bin/portageq envvar USERLAND)"
+if [ "$USERLAND" == "BSD" ] || [ "$USERLAND" == "Darwin" -a -x /bin/gsed ] ; then
        function sed() { gsed "$@"; }
Comment 7 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-05-14 18:54:35 UTC
News about it? The gsed problem should be fixed just using gsed as now sed ebuild always install gsed command.

About root/wheel group... why not just use wheel group as for everything?
Comment 8 Jason Stubbs (RETIRED) gentoo-dev 2005-05-14 20:03:16 UTC
Well, will leave the patch in anyway. Otherwise users (few they might be) will run into problems if they upgrade portage but haven't updated sed to a version that installs gsed as well. I'm not sure what you are talking about with root/wheel but it doesn't belong on this bug anyway.
Comment 9 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-05-30 18:04:27 UTC
Removing bsd cc, as this is mainly darwin problems now :) 
Comment 10 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:37 UTC
Fixed on or before 2.0.51.22-r1 
Comment 11 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:26 UTC
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.