PINE64
Gentoo on Pinebook Pro RELEASE - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: Gentoo on Pinebook Pro RELEASE (/showthread.php?tid=8765)

Pages: 1 2 3 4 5 6

RE: Gentoo on Pinebook Pro RELEASE - as400 - 01-21-2020

@jannik2099 thanks for your work.

Can you show me your boot.scr ?

RE: Gentoo on Pinebook Pro RELEASE - jannik2099 - 01-21-2020

@delcaran , sorry, stuff broke because a dependency changed in the repo. There's not really an automated way to do the required things so I manually have to adapt the script every time this happens - I should probably set up an automated test suite

I tried to reproduce this with both the systemd and openrc tarball but couldn't do that, perhaps the repo was updated again? Either way, I've updated the script to run dispatch-conf , which will prompt you to manually merge these changes should they be required (press m, then r, then u). Please download the script again and try in a fresh tarball

@ElektromAn gentoo devs are working on migrating portage to python 3, this is nothing I can influence. Wether people want to use or mask the python 2_7 useflag is their choice

@as400 I use extlinux.conf, see https://github.com/Jannik2099/gentoo-pinebookpro/tree/master/boot . This is what your /boot should look like, with kernel, dtb and if needed initramfs made and installed accordingly

RE: Gentoo on Pinebook Pro RELEASE - ElektromAn - 01-21-2020

(01-21-2020, 10:44 AM)jannik2099 Wrote: @ElektromAn gentoo devs are working on migrating portage to python 3, this is nothing I can influence. Wether people want to use or mask the python 2_7 useflag is their choice
Wrong ;-)
portage aka emerge is *already* working with python > 2.7
This is from my notebook running Sabayon a gentoo flavour.
Code:
elektroman@T450s ~ $ cat /var/db/pkg/sys-apps/portage-2.3.69/USE
abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_python2_7 python_targets_python3_6 rsync-verify userland_GNU xattr
elektroman@T450s ~ $ sudo eselect python list
Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7
  [3]   python3.5

Python 3.6 is active
Anyway

I'm preparing/compiling included a "emerge --depclean" to remove py2, as they call this on gentoo-dev on IRC
I need some to check other (stuff) with gentoo aka /var/db/repos, I'm familiar with old "deprecated" /usr/portrage

Also the thing I discovered ~2 years ago while crosscompiling the new
"eselect repository"

layman is also deprecated
And mixing layman and eselect is a bad idea

I've cloned your repo on git, currently (also) need to setup my "environment" for working on this ;-)
And I must figure out how I do "pull request" via web, I usually do this via mail.

Hopefully this will be done until FOSDEM and I can (if someone whishes) upload this on my webpage

RE: Gentoo on Pinebook Pro RELEASE - jannik2099 - 01-21-2020

Sorry for that wrong claim then, I haven't familiarized myself with the python situation yet.

I had no idea layman was deprecated, I'll try see if I can figure out how to replace it with eselect-repository later. This should shave off a good chunk of the script build time, thanks!

RE: Gentoo on Pinebook Pro RELEASE - ElektromAn - 01-21-2020

No need to say sorry, everyone make mistakes ...
And I've done the most ;-)

Hmmmf,

I remember I have seen some layman code in your repository ...
Ahh you've updated this already

This is for make.conf

Code:
PYTHON_TARGETS="python3_5 python3_6"
PYTHON_SINGLE_TARGET="python3_6"

and emerge
Code:
emerge -O =dev-lang/python:3.5 =dev-lang/python:3.6

now rebuild the stage

From https://wiki.gentoo.org/wiki/Gentoo_Cheat_Sheet

you should run

Code:
emerge --update --newuse --deep --quiet @world
and

Code:
emerge -av --depclean

maybe I missing something ...

RE: Gentoo on Pinebook Pro RELEASE - jannik2099 - 01-21-2020

I'll leave that choice to the user, that's what Gentoo is all about after all. The migration to eselect-repository should now be complete after I pushed my brainfarts twice to master without proofreading...

RE: Gentoo on Pinebook Pro RELEASE - JaceAlvejetti - 01-21-2020

Just got my PBP today, compiling this on an SD at the moment with the help of an old, but updated, Gentoo distcc vm I had stashed from my rpi3 arm64 days, so far only note I have is the script adds the repo based on git but the stage3 didn't have git, unless I missed it you may want to add installing in the instructions, or the script, but either way thanks for all your work!

RE: Gentoo on Pinebook Pro RELEASE - jannik2099 - 01-21-2020

Oh goddamnit, yeah now that I switched to eselect-repository it doesn't pull in git as a dependency anymore... I've added that now

RE: Gentoo on Pinebook Pro RELEASE - delcaran - 01-21-2020

(01-21-2020, 10:44 AM)jannik2099 Wrote: @delcaran , sorry, stuff broke because a dependency changed in the repo. There's not really an automated way to do the required things so I manually have to adapt the script every time this happens - I should probably set up an automated test suite

I tried to reproduce this with both the systemd and openrc tarball but couldn't do that, perhaps the repo was updated again? Either way, I've updated the script to run dispatch-conf , which will prompt you to manually merge these changes should they be required (press m, then r, then u). Please download the script again and try in a fresh tarball
Thanks man, I know keeping track of depencies is a real pain, as a Slackware user and professional developer, I share a lot of that pain Smile
Anyway, I'll keep track of your repo for all the other changes you've main and try something after work.
Thanks again!

RE: Gentoo on Pinebook Pro RELEASE - delcaran - 01-23-2020

(01-21-2020, 11:43 PM)jannik2099 Wrote: Oh goddamnit, yeah now that I switched to eselect-repository it doesn't pull in git as a dependency anymore... I've added that now

Also, the repos.conf directory is missing, I made a pull request on your repo.

Now I'm compiling the musl hardened profile, I'll give some feedback when it ends.

I must had that I tryed this stage3 but emerge says it can't find /usr/portage, which in fact the script deleted before. This error does not happen with the stage3 I'm currently using, but this variability worries me... I really hope that emerging a musl hardened profile with musl vanilla stage3 will not result in errors...