Am Wed, 9 Jul 2014 13:38:23 +0000 (UTC) schrieb James <wirel...@tampabay.rr.com>:
> Hello, Hi, > I use the stable portage tree for most everything. > I use and test quite a few overlays. > Both of these are great. > > But now, I'm hacking a small collection my own ebuilds that focus > on some specific needs and science, which I shall refer to collectively as > local ebuilds. I'm curious how other folks would suggest to keep them > separate from the main portage tree and the overlays, but easily > maintainable on my own workstation. > > > Semantical suggestions via google seem to be dated. > Observanations and other ideas are most welcome for keeping a bunch > of "local" ebuilds managed and reliable on a stable gentoo system > and as much as possible using the standard gentoo system tools. What you are referring sounds a lot like a local overlay :) . I have one myself that I manage with git, and many others have their own. It's not even particularly difficult, especially if you'll be its only user. The Gentoo Wiki even has a page on local overlays, as I just found out: http://wiki.gentoo.org/wiki/Overlay/Local_overlay. Some further thoughts: - Use repoman, even if you're the only user. - Check the portage man page for documentation on the files that configure the overlay that might be of interest (metadata/layout.conf, stuff in profiles/). It might be completely uninteresting to you, but maybe there are some useful features documented there, depending on what your needs are. - If you don't already have one of them, be sure to install gentoo-syntax or ebuild-mode if you'll be writing ebuilds from scratch with vim or emacs. For example: with gentoo-syntax, when you create a new ebuild, it automatically creates a skeleton ebuild, even depending on the category directory you're in at the moment. > tia, > James HTH -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
signature.asc
Description: PGP signature
