Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I did http://lxnay.wordpress.com/2011/11/13/splitting-the-sabayon-overlay/ But I guess it didn't get to Planet Gentoo? (there might have been problems with the feed) -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
El lun, 14-11-2011 a las 20:41 +0100, Fabio Erculiani escribió: I did http://lxnay.wordpress.com/2011/11/13/splitting-the-sabayon-overlay/ But I guess it didn't get to Planet Gentoo? (there might have been problems with the feed) Looks like it's already shown there also :D signature.asc Description: This is a digitally signed message part
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Case closed! woot! -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Yeah Enlik, let me know when you want to finalize the split by adding the repo to git.s.o and perhaps to layman XML stuff (we need to contact layman people). -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
2011/11/11 Fabio Erculiani lx...@sabayon.org: Yeah Enlik, let me know when you want to finalize the split by adding the repo to git.s.o and perhaps to layman XML stuff (we need to contact layman people). -- Fabio Erculiani I would like to do it ASAP because new commits are being added to the current overlay and they need merging... * The current overlay (overlay.git) should be the new Gentoo part, so current overlay/Portage users don't need to change anything - also no need to change anything for layman. The description on gpo.zugaina.org should be updated though: Purpose To provide ebuilds that were created from the Sabayon Linux project such as customized programs, ebuilds not in the official portage, artwork, themes, etc. Bugs to http://bugs.sabayonlinux.org/bugs/;. *Another one, the Sabayon part should be created on git.s.o (please do it, cloning from my one in Github I mentioned - I can't or don't know how to do new git overlays to be listed on the website). This overlay is for internal purposes, so it doesn't need to be listed in layman - unless you want. When you are ready and like this way, let me know so I will update again sabayon.git→master branch to make it contain ebuilds for Gentoo guys only (10 seconds of work since I've already done it in my local branch - if you don't count merging these 10 brand new commits… :P).
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I've done it the Ian way The best way... Thanks for your great work here Enlik, think we just need to put both of these repositories onto git.s.o now, and we are good to go. Exciting!
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
2011/10/30 Sławomir Nizio slawomir.ni...@sabayon.org: Ebuild sorting done, commits squased into one and pushed to another branch, gentoo-squashed-merge (note how cool name). Need to do then other stuffs like with sets/*. Nice! Where's the new repo? I need to add it to cgit (and to build server overlays, and to layman xml crapshit I guess) If someone has a suggestion on something, speak up! I'm confused with: sets and profile/updates - they refer to packages that are intended to be in these two overlays. Don't know if there's a single set that refers to packages from both, but there is such problem for profiles/updates files. Keep profile/updates in both overlays, they will now live separate lifes :P - My idea about sets - KISS, remove em all from for Gentoo overlay driven by idea that if someone (the chroots?) has for Sabayon overlay attached, he has the for Gentoo one in use too. So if a set that is going to be in for Sabayon contains app-misc/w00t that has to be in for Gentoo and app-misc/ugh that has to be in the other one, all dependencies will be met. Unless PMs are more strict about this and require all packages in set to be in Portage or strictly the overlay the sets/blah file is in. Will test… keep sets only in our overlay. It's just our stuff. - The second thingy, profile/updates. If say 3Q-1892 :P contains app-misc/bleh that is in for Sabayon and app-misc/argh that is in for Gentoo… I think those files should be split too (atoms moved to relevant directory) and PMs will be happy. -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
2011/10/31 Fabio Erculiani lx...@sabayon.org: 2011/10/30 Sławomir Nizio slawomir.ni...@sabayon.org: Ebuild sorting done, commits squased into one and pushed to another branch, gentoo-squashed-merge (note how cool name). Need to do then other stuffs like with sets/*. Nice! Where's the new repo? I need to add it to cgit (and to build server overlays, and to layman xml crapshit I guess) The other one is not made yet, I was writing about this: http://git.sabayon.org/overlay.git/log/?h=gentoo-squashed-merge it's based on the 'gentoo' git branch, but all split commits are merged into one and was synced with master. What is left is the stuff I asked about, and after sorting that out I will make the other overlay. :) If someone has a suggestion on something, speak up! I'm confused with: sets and profile/updates - they refer to packages that are intended to be in these two overlays. Don't know if there's a single set that refers to packages from both, but there is such problem for profiles/updates files. Keep profile/updates in both overlays, they will now live separate lifes :P OK, so I'll simply duplicate them. In case something complains it could be handled in a less pleasant way, hehe. - My idea about sets - KISS, remove em all from for Gentoo overlay driven by idea that if someone (the chroots?) has for Sabayon overlay attached, he has the for Gentoo one in use too. So if a set that is going to be in for Sabayon contains app-misc/w00t that has to be in for Gentoo and app-misc/ugh that has to be in the other one, all dependencies will be met. Unless PMs are more strict about this and require all packages in set to be in Portage or strictly the overlay the sets/blah file is in. Will test... keep sets only in our overlay. It's just our stuff. OK, cool! - The second thingy, profile/updates. If say 3Q-1892 :P contains app-misc/bleh that is in for Sabayon and app-misc/argh that is in for Gentoo... I think those files should be split too (atoms moved to relevant directory) and PMs will be happy. -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Ebuild sorting done, commits squased into one and pushed to another branch, gentoo-squashed-merge (note how cool name). Need to do then other stuffs like with sets/*. If someone has a suggestion on something, speak up! I'm confused with: sets and profile/updates - they refer to packages that are intended to be in these two overlays. Don't know if there's a single set that refers to packages from both, but there is such problem for profiles/updates files. - My idea about sets - KISS, remove em all from for Gentoo overlay driven by idea that if someone (the chroots?) has for Sabayon overlay attached, he has the for Gentoo one in use too. So if a set that is going to be in for Sabayon contains app-misc/w00t that has to be in for Gentoo and app-misc/ugh that has to be in the other one, all dependencies will be met. Unless PMs are more strict about this and require all packages in set to be in Portage or strictly the overlay the sets/blah file is in. Will test… - The second thingy, profile/updates. If say 3Q-1892 :P contains app-misc/bleh that is in for Sabayon and app-misc/argh that is in for Gentoo… I think those files should be split too (atoms moved to relevant directory) and PMs will be happy.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I've written above about another solution (make 2 git repos, every one based on the current one), so commit history for every ebuild/eclass is preserved (in fact it's preserved for deleted files, but it's less comfortable/common to access - you need to know such a file/dir was there). Downside: size of .git directory is doubled (72 MB on my system without doing gc). Take a look at the two my messages above please. And second it'd be some more work to do rather than then transfer out the sabayon specific ebuilds (there are less of them and are pretty obvious). Do we need that git history in the two overlays, after all? I'd say can live without it and do as you wrote. Any thoughts on this?
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Can live without history. (especially my stupid EPIC mistakes) 2011/9/25 Sławomir Nizio slawomir.ni...@sabayon.org: I've written above about another solution (make 2 git repos, every one based on the current one), so commit history for every ebuild/eclass is preserved (in fact it's preserved for deleted files, but it's less comfortable/common to access - you need to know such a file/dir was there). Downside: size of .git directory is doubled (72 MB on my system without doing gc). Take a look at the two my messages above please. And second it'd be some more work to do rather than then transfer out the sabayon specific ebuilds (there are less of them and are pretty obvious). Do we need that git history in the two overlays, after all? I'd say can live without it and do as you wrote. Any thoughts on this?
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I want history to be preserved. Thanks. -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I guess its cp then git rm then :) Lets just start it, enough chit chat. On 25 September 2011 13:35, Fabio Erculiani lx...@sabayon.org wrote: I want history to be preserved. Thanks. -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
On Sun, Sep 25, 2011 at 5:39 PM, Ian Whyman v00...@v00d00.net wrote: I guess its cp then git rm then :) Lets just start it, enough chit chat. Right! Feel free to go ahead -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Yeah that is my home server pushing a backup of my sabayon git repos to github... eheheh -- Fabio Erculiani
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Let me quickly introduce my simple idea.
(tl;dr: create copy of current overlay, remove Sabayon-only stuff from
it, then using some wizardy make the second overlay.)
I create a temporary throw-away git repository. It will be a copy of
current 'sabayon' overlay.
From it all Sabayon-only stuff will be removed (1).
When it's done any only stuff that Gentoo users will like is in it,
I'll do this:
cd sabayon
# first take care of new changes done after copying the overlay, then
rm -r * # .git will be left untouched
cp -r $beforementionedgitrepo/* .
# at this point git will see removed files, they're not needed, remove them:
git rm $everything_not_needed
git commit -m 'split overlay, credits to '
git push
- one commit and all Sabayon-only stuff will be removed from current
sabayon overlay (I propose not to change this overlay's name).
So, now we have a Gentoo-friendly overlay. We take the list of what
is in it {modify it a bit, make sure it's ok…}, and feed the script
I've shown above which will create Sabayon-only overlay. Profit.
Because the segregation would be done on external git repo, current
work wouldn't be interrupted.
--
(1) The idea of doing it using a temp. git repo is to ease collaboration on it.
Not to make anyone who wants to help (Ian? :P) make double work or
collisions, one person can claim he will do these-and-those categories
and then mark them as done in a file (echo done app-misc blah;
commit).
--
Things to consider when choosing where a package belongs (useful for
me when I forget):
- is it useful for Gentoo users,
- does it depend on Sabayon-specific packages (like split ones - in
this case make it go to 'sabayon-distro' (or whatever you call it) or
fix it),
- is it in Portage already, if so: if it's a version upgrade or fix
Gentoo users may want, probably make it go into Gentoo-friendly
overlay,
- more?
About other files:
- eclass - if any package requires it, leave it in overlay unless it
makes some unwanted changes for Gentoo folks.
--
As Ian mentioned, enough words, let's do something. :) If someone
doesn't have a better idea or doesn't make me some harm due to my
verboseness, I'll create said temp. git repository on GitHub later
when I have time. I'll give rw access for Ian and Fabio, because I
know what's your GitHub accounts, the rest who wants it should ping
me.
Thanks.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Yes. Finally! Been on about this for ages :) On Sep 22, 2011 5:22 PM, Pacho Ramos pa...@gentoo.org wrote: El jue, 22-09-2011 a las 16:33 +0200, Fabio Erculiani escribió: I have this on my TODO Pacho, it will happen at some point and I'll ping you back. Thanks, Fine, thanks a lot :D
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
I agree with the idea ... I honestly do not know how much work effort and time would be involved with this project. Why I am only a beta tester ;-) Really, what would be the steps and time needed to do such a project? On a scale of 1 to 5 and 5 being easy ... where would it be? Any time sabayon can add upstream, imho is a good thing ... I really have no concept of what effort it would be involved. On Sat, Sep 24, 2011 at 5:34 PM, Ian Whyman v00...@v00d00.net wrote: Yes. Finally! Been on about this for ages :) On Sep 22, 2011 5:22 PM, Pacho Ramos pa...@gentoo.org wrote: El jue, 22-09-2011 a las 16:33 +0200, Fabio Erculiani escribió: I have this on my TODO Pacho, it will happen at some point and I'll ping you back. Thanks, Fine, thanks a lot :D
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Yes, whatever needs to be done. Fabio is the infra :), though, what I'd need mainly to do is putting ebuilds in the proper overlay, I think. There was no discussion about technical implementation of the idea so I currently can't see any place to start.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
New got repo, then transfer out the sabayon specific ebuilds (there are less of them and are pretty obvious). Profit. Ill be back soon so will help/be a reference as needed. On Sep 24, 2011 10:16 PM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Yes, whatever needs to be done. Fabio is the infra :), though, what I'd need mainly to do is putting ebuilds in the proper overlay, I think. There was no discussion about technical implementation of the idea so I currently can't see any place to start.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
El jue, 22-09-2011 a las 16:33 +0200, Fabio Erculiani escribió: I have this on my TODO Pacho, it will happen at some point and I'll ping you back. Thanks, Fine, thanks a lot :D signature.asc Description: This is a digitally signed message part
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
El lun, 19-09-2011 a las 17:42 -0500, Mitch Harder escribió: On Mon, Sep 19, 2011 at 2:49 AM, Joost Ruis joostr...@gmail.com wrote: Fabio explained the idea to me some weeks ago, but let me again confirm I agree. (o: 2011/9/19 Sławomir Nizio slawomir.ni...@sabayon.org: Speaking about git history, don't know why I didn't think of it the first place: it could be done this way (idea): cp -r overlay overlay-gen mv overlay overlay-sab rm overlay-gen/sab-stuff rm overlay-sab/gen-stuff ZzZ. This idea seems to be profitable for Gentoo users. I've sometime thought about it. Should it be done or not, let me share my thoughts of main disadvantages for Sabayon I can think of, for fruitful discussion. - A git repository created from scratch wouldn't have ebuilds etc. history (logs). But if for example the Gentooish overlay is made of current sabayon overlay from which Sabayon stuff is removed, git history of deleted files would be still available in it. I don't know if that could be made better, but if not, maybe this problem could be ignored (of course if answer for this proposal is yes). I can only think of spliting the overlay *not* into two physical git repositories, but into two branches. Question here: would it be a comfortable solution for the maintainers - hmm, it could work. But I'm not that sure layman-and-others support it. - It's possible some eclasses and/or virtuals would need to be shared and maintained simultaneously in the two overlays, but it's IMO no big thing. I don't know how it looks from the perspective of the infrastructure, so I won't say anything in this regard. On the other hand: what good could it bring to Sabayon - more fame. :) I generally support this proposal. But please understand this has the potential to involve a significant amount of manual labor, so it may take a while to make it happen. Then again, it may end up being easier. No problem at all, I really understand you as I neither have much time ;) Best regards :) signature.asc Description: This is a digitally signed message part
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
Fabio explained the idea to me some weeks ago, but let me again confirm I agree. (o: 2011/9/19 Sławomir Nizio slawomir.ni...@sabayon.org: Speaking about git history, don't know why I didn't think of it the first place: it could be done this way (idea): cp -r overlay overlay-gen mv overlay overlay-sab rm overlay-gen/sab-stuff rm overlay-sab/gen-stuff ZzZ. This idea seems to be profitable for Gentoo users. I've sometime thought about it. Should it be done or not, let me share my thoughts of main disadvantages for Sabayon I can think of, for fruitful discussion. - A git repository created from scratch wouldn't have ebuilds etc. history (logs). But if for example the Gentooish overlay is made of current sabayon overlay from which Sabayon stuff is removed, git history of deleted files would be still available in it. I don't know if that could be made better, but if not, maybe this problem could be ignored (of course if answer for this proposal is yes). I can only think of spliting the overlay *not* into two physical git repositories, but into two branches. Question here: would it be a comfortable solution for the maintainers - hmm, it could work. But I'm not that sure layman-and-others support it. - It's possible some eclasses and/or virtuals would need to be shared and maintained simultaneously in the two overlays, but it's IMO no big thing. I don't know how it looks from the perspective of the infrastructure, so I won't say anything in this regard. On the other hand: what good could it bring to Sabayon - more fame. :)
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
On Mon, Sep 19, 2011 at 2:49 AM, Joost Ruis joostr...@gmail.com wrote: Fabio explained the idea to me some weeks ago, but let me again confirm I agree. (o: 2011/9/19 Sławomir Nizio slawomir.ni...@sabayon.org: Speaking about git history, don't know why I didn't think of it the first place: it could be done this way (idea): cp -r overlay overlay-gen mv overlay overlay-sab rm overlay-gen/sab-stuff rm overlay-sab/gen-stuff ZzZ. This idea seems to be profitable for Gentoo users. I've sometime thought about it. Should it be done or not, let me share my thoughts of main disadvantages for Sabayon I can think of, for fruitful discussion. - A git repository created from scratch wouldn't have ebuilds etc. history (logs). But if for example the Gentooish overlay is made of current sabayon overlay from which Sabayon stuff is removed, git history of deleted files would be still available in it. I don't know if that could be made better, but if not, maybe this problem could be ignored (of course if answer for this proposal is yes). I can only think of spliting the overlay *not* into two physical git repositories, but into two branches. Question here: would it be a comfortable solution for the maintainers - hmm, it could work. But I'm not that sure layman-and-others support it. - It's possible some eclasses and/or virtuals would need to be shared and maintained simultaneously in the two overlays, but it's IMO no big thing. I don't know how it looks from the perspective of the infrastructure, so I won't say anything in this regard. On the other hand: what good could it bring to Sabayon - more fame. :) I generally support this proposal. But please understand this has the potential to involve a significant amount of manual labor, so it may take a while to make it happen. Then again, it may end up being easier.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
In my opinion, which is not worth much. If there was anyway that we could make sabayon more accessible to gento and vise versa, I am all for it as a great idea. The gentoo community is what has made sabayon possible in the first place. Sabayon did have no help in the beginning from gentoo. Since those times, sabayon and gentoo is growing what I feel is a good relationship with each other. I do not know how much time and effort it would take on sabayon devs, they are under paid and over worked as it is. If this effort from sabayon would further improve the growing relationship with gentoo, I think it would be time well spent. We all know gentoo is awesome, so is sabayon ... anytime we can work together, I think it is an improvement that will only better both sides. Just my opinion with out knowing all the facts. On Mon, Sep 19, 2011 at 10:42 PM, Mitch Harder mitch.har...@sabayonlinux.org wrote: On Mon, Sep 19, 2011 at 2:49 AM, Joost Ruis joostr...@gmail.com wrote: Fabio explained the idea to me some weeks ago, but let me again confirm I agree. (o: 2011/9/19 Sławomir Nizio slawomir.ni...@sabayon.org: Speaking about git history, don't know why I didn't think of it the first place: it could be done this way (idea): cp -r overlay overlay-gen mv overlay overlay-sab rm overlay-gen/sab-stuff rm overlay-sab/gen-stuff ZzZ. This idea seems to be profitable for Gentoo users. I've sometime thought about it. Should it be done or not, let me share my thoughts of main disadvantages for Sabayon I can think of, for fruitful discussion. - A git repository created from scratch wouldn't have ebuilds etc. history (logs). But if for example the Gentooish overlay is made of current sabayon overlay from which Sabayon stuff is removed, git history of deleted files would be still available in it. I don't know if that could be made better, but if not, maybe this problem could be ignored (of course if answer for this proposal is yes). I can only think of spliting the overlay *not* into two physical git repositories, but into two branches. Question here: would it be a comfortable solution for the maintainers - hmm, it could work. But I'm not that sure layman-and-others support it. - It's possible some eclasses and/or virtuals would need to be shared and maintained simultaneously in the two overlays, but it's IMO no big thing. I don't know how it looks from the perspective of the infrastructure, so I won't say anything in this regard. On the other hand: what good could it bring to Sabayon - more fame. :) I generally support this proposal. But please understand this has the potential to involve a significant amount of manual labor, so it may take a while to make it happen. Then again, it may end up being easier.
Re: [sabayon-dev] About splitting sabayon overlay to easily use it on Gentoo
already easy to handle locally, add the overly, mask the overlay, ln -s what ever you want from the overlay to wherever else you want. Why ask someone else to do something because your being lazy? On Sun, Sep 18, 2011 at 10:22 AM, Wolfden wolf...@gmail.com wrote: yes I agree if it's dependency issues On Sun, Sep 18, 2011 at 2:15 PM, Vitovt vit...@grusha.org.ua wrote: Very good idea to split Sabayon stuff and General stuff. It is because of dependencies sometimes people don't need to change KDM theme, bud would like to install unmasked and verified KDE. Also with others packets. It will be easier to use by normal Gentoo users and also it will be easier to add fixes and offer patches. -- Vitovt Керівник проекту Груша.org.ua e-mail: vit...@grusha.org.ua IRC: chat.freenode.net #grusha 73 2011/9/18 Pacho Ramos pa...@gentoo.org El dom, 18-09-2011 a las 12:47 -0400, Wolfden escribió: Why can't you install the packages now with one overlay? It's not like you gonna emerge the whole layman anyway. I can add the sunrise overlay, but may only install one or two packages. This request seems odd. -- KJS ~wolfden~ Last time I tried to use sabayon overlay portage wanted to install a lot of packages (for example, gnome packages) from sabayon overlay instead of main tree, while I only wanted sabayon overlay to install some packages not yet available in gentoo. This is the reason why I would like to be able to add an overlay only with packages not available in gentoo yet. -- KJS ~wolfden~
