On Tuesday 21 June 2005 20:42, Aron Griffis wrote: > In other words, I think you need to do some work in an overlay so that > you can present a real list of affected ebuilds and utilites, rather > than stating that you "don't really know" Well this was just a discussion, no work should really start for now :)
> Rather > I want to suggest the next step is a more complete investigation, > rather than committing any changes to the portage tree. That was for sure :) No big change to do before something working is already there.. like we're doing for G/FBSD. > Why is that a long-term goal? What are the advantages/disadvantages > of the eselect method compared to the aliases? Because aliases makes difficult to follow the flow of an ebuild because you read "sed" and but is gsed that's called.. similarly for other tools. Aliases are like #defines into C code.. makes debug harder, very harder. > As Az mentioned, this is really going to be annoying unless all the > sed programs available support -i BSD does, and I think we can make a prerequisite to be used in portage that the system's sed supports -i. The only problem is with the options orders.. sed -i -e expr works, sed -e -i expr or sed -e expr -i doesn't. > I'll re-iterate: I'm not trying to shoot down this idea completely. > I just want to have a general understanding that it's the *right* > option before making treewide changes. That's why we're discussing it :) -- Diego "Flameeyes" Pettenò Gentoo Developer - http://dev.gentoo.org/~flameeyes/ (Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)
pgpVXvhqHVbj3.pgp
Description: PGP signature
