On Tuesday 08 January 2008, Daniel Iliev wrote: > On Tue, 8 Jan 2008 15:11:09 +0200 > > Alan McKinnon <[EMAIL PROTECTED]> wrote: > > A much better way would be to modify the ebuild to do what you > > want, then copy it to a local overlay. Portage will use your > > overlay in preference to the portage tree. You just have to then > > watch out for newer versions to hit the tree which will supercede > > your custom ebuild, and modify those new versions similarly. > > Yes, may be it's time for me to learn how to write an ebuild. My > problem is that it seems to me too much work just to maintain a > few occasional packages locally. ;-)
It is a reasonable amount of work to read the man pages and so on, but I found it was well worth the trouble. Now when I read an ebuild I understand what I'm seeing, before it was just meaningless stuff. Am I correct in saying you plan to emerge mplayer with a few extra params and not much else customizing? In that case the mods you will make are simple and need to be done just once. Then paste the same changes into a new ebuild each time you want to upgrade > > There's an environment variable EXTRA_ECONF intended for *users* to > > add extra configure options when emerging, but I have heard bad > > things about using this. Don't know the details, perhaps someone > > else who does will post in response. > > Yes, I'm aware of EXTRA_ECONF and I use it via /etc/portage/bashrc. > ( explained w/ example by Mr. Bo Andresen: http://tinyurl.com/39c74x > ) It never caused problems here. Interesting. I must find out more :-) > I want to change the "./configure --params" for sure but perhaps I'd > need to alter several source files. I'm not sure if > /etc/portage/bashrc could do the work in the latter case but it's an > idea that never occurred to me before and I'm going to explore. > > > Finally, you could just mask out mplayer entirely and build it from > > source using the default DESTDIR of /usr/local. It's not a complete > > unistall solution, but at least it doesn't collide with portage's > > installs in /usr/ > > Why mask? Just a safety net really, in case you one day forget and run 'emerge mplayer'. Not necessary for operation :-) -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
