On Sunday August 11 2024 12:33:41 Ryan Carsten Schmidt wrote:

>I seem to have misremembered. Lots of portgroups use namespaces but only for 
>procedures, not options.

And internal variables. That's the use case for me here too; I just use options 
variables "internally" in a number of cases because of the extra features they 
provide.

>This makes sense since options are intended to be used by portfiles whereas 
>we've always said that anything in a namespace should not be used in a 
>portfile (though there are many examples of ports that violate this out of 
>necessity that some things in base are not accessible to portfiles in another 
>way). 

If you ask me there isn't much difference from the user point of view between 
controlling variables organised in fake namespaces (foo.bar) or in real ones 
(foo::bar). And even from a development point of view there isn't much useful 
that the latter offer over the former as far as PortGroup and Portfile 
programming is concerned. Both allow to avoid clashes.

That's also why this isn't really an issue for me, except that I wouldn't mind 
understanding what changed and if this is just a side-effect or something more.

Reply via email to