On Friday 23 September 2005 06:09, Chris Gianelloni wrote: > it would be a good idea to give the user some way of knowing that a > package requires some additional purchased (or otherwise obtained) > portion that is not a distfile/tarball.
It would be a good idea, indeed. RESTRICT="purchase" or somesuch parallel to RESTRICT="fetch" would solve this just as well. However, whenever adding new stuff like this, as a portage developer, I always ask what use of it can be made by portage? I can't see anything other than passing the information to a user interface to blink some text at the user... Overloading RESTRICT="fetch" to include this case seems like the best method to me. Really, what's the difference between fetch-restricted and "purchase -restricted"? From a portage point of view, they both require the user to dance through some hoops before getting access and there's not really any important difference beyond that. So, if RESTRICT="fetch" were to be overloaded, there is the issue of both fetch-restricted and non-fetch-restricted downloads in the one package. I would think this issue exists already for some packages. How is it dealt with at the moment? -- Jason Stubbs
pgpkUAWJUcaz0.pgp
Description: PGP signature
