Profile

[Alessandro-Barbieri]

No description provided.

[Alessandro-Barbieri]

How I can remove the duplicate commits?

[kiwifb]

I don't really know, but it is alright I'll squash the commits anyway. Will review a bit later when I have more time.

[kiwifb]

Sorry, I haven't made much time to review this yet. I will do when I can.

[kiwifb]

OK, I had a first look at things. I am not sure about this, I don't think many other projects offer profiles and I am starting to see why. You are reducing the number of version of sage supported, not necessarily a bad thing, but it should be explicit.
I would have preferred if profile was proposed as an alternative rather the only way of getting the settings. It should be possible to re-add the method about linking files by just pointing to different files. Although it is quite annoying in that the new version lose the ::sage-on-gentoo bits for some packages. I don't believe masking packages from the main tree is a good solution (especially if you bring a different overlay with competing ebuilds).
It is also unclear what impact it will have on my development workflow.
It is also clear that if you want to keep your current profile and add the sage-on-gentoo one to it, it is more work.
At least, unlike what I feared, an hybrid profile doesn't need a lot of maintenance (as in "you don't need to recreate it for upgrades"). That's a neutral point for it (not better, not worse).

[Alessandro-Barbieri]

OK, I had a first look at things. I am not sure about this, I don't think many other projects offer profiles and I am starting to see why.

The only other overlay with profiles that I know is the bentoo overlay
This overlay, unlike the others, doesn't provide only ebuilds but require additional setup in order to work

You are reducing the number of version of sage supported, not necessarily a bad thing, but it should be explicit.

I can readd them but in a profile for every version (I have to change the naming then)

I would have preferred if profile was proposed as an alternative rather the only way of getting the settings. It should be possible to re-add the method about linking files by just pointing to different files.

I can restore the files deleted as symlinks or list the 1:1 correspondent new file

Although it is quite annoying in that the new version lose the ::sage-on-gentoo bits for some packages. I don't believe masking packages from the main tree is a good solution (especially if you bring a different overlay with competing ebuilds).

I had to remove the explicit :: because is an illegal syntax for this kind of files

It is also unclear what impact it will have on my development workflow.

You will have more granularity, for example: you can add specific masking/useflags/keywording/unmasking for a future ppc64 profile that will affect only that profile

It is also clear that if you want to keep your current profile and add the sage-on-gentoo one to it, it is more work.

I don't think is a lot of work to do (if you want to keep eselect profile working) otherwise a faster method is to unlink /etc/portage/make.profile and replace it wit a text file containing, for example:

gentoo:hardened/linux/amd64
sage-on-gentoo:default/linux/amd64/13.0/stable/bindoc

[kiwifb]

The bit about ppc64 is interesting. Lots of keywords are just missing, and some useflags are masked (ecls for example). However I won't have access to that hardware forever. By the end of the year I am expecting to be ppc64-less and end that adventure then.