On Wednesday 14 December 2005 09:52, Ciaran McCreesh wrote: > On Wed, 14 Dec 2005 09:11:51 +0900 Jason Stubbs <[EMAIL PROTECTED]> > > wrote: > | newsdir="$(portageq envvar PORTDIR)/metadata/news" > | newsdir="$(portageq newsdir gentoo)" > | > | Both have one level of indirection. The first has two hard coded > | elements. The first has one. Where is the massive over-indirection? > | > | The second allows future changes. The first does not. Where does the > | specification come into it? All that would be needed is to allow a > | user a method to name overlays and it'd be useful straight off the > | bat. > > The former relies upon existing, widely used functionality together > with a well-defined path. The latter has some magic hard-coded name > voodoo (what's a 'gentoo'?) and is still stuck only supporting a single > location.
What's a 'PORTDIR'? What's a 'metadata'? Outside of portage, these are also magic name voodoo. But I've grown tired of your imperfect circles. I think your design sucks and you think that my solution to making it not suck is too soon. The solution to that seems simple to me. Rather than have 'package manager' do anything, just have it provide hooks that will allow you to do your thing at the times you want. Good luck with solving the "news in overlays" bug when it comes in. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
