Date: Fri, 16 Sep 2011 11:04:10 +0100 From: "Klaus T. Aehlig" <aehlig@linta.de> To: ??ukasz W??sikowski <lukasz@wasikowski.net> Cc: freebsd-ports@freebsd.org Subject: Re: overlays Message-ID: <20110916100410.GA49494@kta1c10.sesnet.soton.ac.uk> In-Reply-To: <4E731A92.1050700@wasikowski.net> References: <20110912230943.GD33455@guilt.hydra> <4E6E99BC.4050909@missouri.edu> <1315905051.1747.208.camel@xenon> <4E6F8A50.9060205@gmx.de> <1315942042.1747.258.camel@xenon> <4E6FD71D.9010207@gmx.de> <20110914181553.f6d31b0f.cjr@cruwe.de> <4E722F3F.3030606@wasikowski.net> <20110916062452.GA57167@curry.linta.de> <4E731A92.1050700@wasikowski.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Simplicity. [...] I've got ca. 70 Gentoo servers and I want my own > portage overlay. Thank you very much for that explanation! I was thinking in a different direction, as the number of machines I have is quite limited, each with very specific needs. As long as it is only about adding new ports, I would probably have /usr/ports/local a checkout of my personal repository with the rest of /usr/ports a checkout of the official repository (cvs allows this and cvs update will tacitly update each directory form the repository it belongs). But as I said, I have no practical experience with the same overlay on a bulk of machines. My thought was in the direction of tweaking a single machine to its very specific needs while keeping maintenance of the tweaked machine simple. So thanks for clarifying this and best regards, Klaus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110916100410.GA49494>