A new Gentoo for Mac OSX installer should be created that includes fixes for: - updated version of portage (to avoid collision-protect bugs on them) - a better bootstrap script that sets the correct CHOST variable - the FETCH_COMMAND should include -f to deal with failing downloads/sites slightly off topic: - portage created users should not be included on the list of users when logging on. I guess this is unrelated to the installer, but I felt it worth mentioning here. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Ok, I have an updated installer locally, I want to wait for the next stable version of portage before releasing, as it will have initial support for EAPI. (In reply to comment #0) > A new Gentoo for Mac OSX installer should be created that includes fixes for: > - updated version of portage (to avoid collision-protect bugs on them) This should be fixed. > - a better bootstrap script that sets the correct CHOST variable > - the FETCH_COMMAND should include -f to deal with failing downloads/sites > This is fixed. > slightly off topic: > - portage created users should not be included on the list of users when logging on. > I guess this is unrelated to the installer, but I felt it worth mentioning here. I fixed this for the pkg installer, enewuser still needs to be updated. Setting the nefinfo property "change 0" is the fix. I also removed the `alias emerge='sudo emerge'` to make it a little more gentooey. I would also like to offer a couple different installers, one minimal(~500K, pretty much what we have now) as well as a 'full' install (~should be ~24MB, basically all the utils that `emerge system` pulls in).
*** Bug 67600 has been marked as a duplicate of this bug. ***
w00t! One thing I don't really agree on, which is the release of it. Only if a new portage release is next week, I'd say it is profitable to wait, otherwise, why waiting for more bugs on 'broken portage' and 'portage update collides'. Or I miss a point here, but if you already have the installer floating around, it should be a no cost operation to let it go live.
Next stable portage was supposed to have been released as testing this weekend, probably stable in a couple weeks. I wanted to wait as the addition of EAPI is fairly substantial, especially for our upcoming overlay work. And I'd rather not have to issue 2 installers in quick succession....
(In reply to comment #2) > > slightly off topic: > > - portage created users should not be included on the list of users when logging on. > > I guess this is unrelated to the installer, but I felt it worth mentioning here. > > I fixed this for the pkg installer, enewuser still needs to be updated. Setting the nefinfo property > "change 0" is the fix. Setting said users' shell to /bin/false works, too.
some users generated by portage need a shell (usually /bin/bash) to have the respective daemon/program using it running correctly
new problem: on a fresh Gentoo for OSX install etc-update is broken: Scanning Configuration files... Automerging trivial changes in: etc-update.conf The following is the list of files which need updating, each configuration file is followed by a list of possible replacement files. 1) /etc/dispatch-conf.conf /etc/._cfg0000_dispatch-conf.conf 2) /etc/make.conf.example /etc/._cfg0000_make.conf.example Please select a file to edit by entering the corresponding number. (don't use -3 or -5 if you're unsure what to do) (-1 to exit) (-3 to auto merge all remaining files) (-5 to auto-merge AND not use 'mv -i'): 1 /usr/sbin/etc-update: line 243: less": command not found 1) Replace original with update 2) Delete update, keeping original as is 3) Interactively merge original with update 4) Show differences again Please select from the menu above (-1 to ignore this update): ^C aphrodite:/etc root# The solution (which is IMHO quite stupid, but I don't know another way to solve it) is to remove all quotes from /etc/etc-update.conf, which solves the problem, and also finds more patched to be trivially enough to simply apply (such as the above visible make.conf.example, which indeed should have)
Have we seen any other suggestions? Adding 90329 to the blocked list as it is also related to the installer.
Conclusion of the story: you'll wait forever and never release the work you did. Now it's gone forever.
