Closed cnd closed 11 years ago
usually I handle manifests with ebuild digest
Why remove all keywords?
Because everyone will automatically upgrade to these pre-release versions which most users won't want On 24 Sep 2013 10:43, "Heather" notifications@github.com wrote:
usually I handle manifests with ebuild digest
Why remove all keywords?
— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/pull/41#issuecomment-24989462 .
Agreed. But it will not be comfort for me. And in the same time I like your work in way of getting multilib there.
I used to have 3.9.90, now 3.9.92 gnome and then discovered this work. I had two different libraries set, without multilib on my overlay and with multilib on this overlay fork. Now I used to bump things only in my overlay but based on multilib. Also my overlay is syncing with gnome overlay.
So as you see I've got complete mess with it for now.
Possible variants to get things cleaner:
Any other ideas?
You'd just need to add the ebuilds to your keywords file and they will work for you
But these could potentially break things for other people. You could also ask the other overlay to add in multilib support - its all the rage at the moment... On 24 Sep 2013 11:33, "Heather" notifications@github.com wrote:
Agreed. But it will not be comfort for me. And in the same time I like your work in way of getting multilib there.
I used to have 3.9.90, now 3.9.92 gnome and then discovered this work. I had two different libraries set, without multilib on my overlay and with multilib on this overlay fork. Now I used to bump things only in my overlay but based on multilib. Also my overlay is syncing with gnome overlay.
So as you see I've got complete mess with it for now.
Possible variants to get things cleaner:
- move everything new to my overlay with manual syncing.
- merge overlays and mask all the new stuff. support ability to unmask new stuff by linking some file.
Any other ideas?
— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/pull/41#issuecomment-24992149 .
That will go, but...
How can I separate all experimental ebuilds from live ebuilds?
I'll be doing a mass update tonight and hopefully removing a lot of builds that have been upsteamed
Yes I just wanted to point upstream emul updates )
for now this pull provides a bit weird updates... i should re-fork for quality I think...
If you remove all the keywords from the new pre-release ebuilds I'll happily merge it
Did you run repoman fix too?