| 1 |
On Sun, Mar 18, 2018 at 01:24:59AM +0000, M. J. Everitt wrote |
| 2 |
|
| 3 |
> May I ask whether you've posted to the -musl ML about this, at all? |
| 4 |
|
| 5 |
I wasn't aware of it. I'll check it out. |
| 6 |
|
| 7 |
> In my limited experience of amd64 musl, you first install git without |
| 8 |
> gpg, and layman from the regular portage tree ONLY, per Step3 |
| 9 |
|
| 10 |
That's *EXACTLY* what I was trying to do (32-bit install). Let's just |
| 11 |
say that I ran into various breakages. It refuses to build with the |
| 12 |
default make.conf. |
| 13 |
|
| 14 |
It wants me to change USE flags, keyword and unmask some packages, |
| 15 |
etc. The net result is that it ends up trying to build almost 60 |
| 16 |
packages... and dying in the process, as mentioned in the comments of |
| 17 |
step 5. |
| 18 |
|
| 19 |
> and THEN run step 5 later on .. hence why 5 > 3. After that you can |
| 20 |
> remove the package.use entry, sync up, and reinstall git from the |
| 21 |
> musl overlay .. iirc.. So I'm not sure where I see your "circular |
| 22 |
> dependency" issue? |
| 23 |
|
| 24 |
I can't get past the emerge in step 3. |
| 25 |
|
| 26 |
> It is conceivable that the relevant stage3 for *musl could have git and |
| 27 |
> layman pre-installed by tweaking their profile to add these packages if |
| 28 |
> it's felt necessary & appropriate. It would certainly make the install |
| 29 |
> process a lot simpler & smoother ... |
| 30 |
|
| 31 |
+1000 |
| 32 |
|
| 33 |
-- |
| 34 |
Walter Dnes <waltdnes@××××××××.org> |
Archives