Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread Ryan Schmidt
On Oct 26, 2015, at 7:22 AM, René J.V. Bertin wrote: > On Monday October 26 2015 12:59:38 Rainer Müller wrote: > >> My idea of 'port dump' was to only output options with their values once >> after parsing the Portfile. > > How would that be different from what `port info` does currently? > >>

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread Rainer Müller
On 2015-10-26 13:46, Joshua Root wrote: > On 2015-10-26 23:22 , René J.V. Bertin wrote: >> On Monday October 26 2015 12:59:38 Rainer Müller wrote: >> >>> My idea of 'port dump' was to only output options with their values once >>> after parsing the Portfile. >> >> How would that be different from w

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread Joshua Root
On 2015-10-26 23:22 , René J.V. Bertin wrote: > On Monday October 26 2015 12:59:38 Rainer Müller wrote: > >> My idea of 'port dump' was to only output options with their values once >> after parsing the Portfile. > > How would that be different from what `port info` does currently? The purpose o

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread René J . V . Bertin
On Monday October 26 2015 12:59:38 Rainer Müller wrote: > My idea of 'port dump' was to only output options with their values once > after parsing the Portfile. How would that be different from what `port info` does currently? > You can't get the value after a specific phase without execution of

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread Rainer Müller
On 2015-10-26 11:53, René J.V. Bertin wrote: > On Monday October 26 2015 11:06:13 Rainer Müller wrote: >> >> If we would want to dump all possible options, we also would need >> to keep a list when they are defined. That would be necessary to be >> added in port1.0/portutil.tcl. > > Yeah, I saw t

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread René J . V . Bertin
On Monday October 26 2015 11:06:13 Rainer Müller wrote: > > If we would want to dump all possible options, we also would need to > keep a list when they are defined. That would be necessary to be added > in port1.0/portutil.tcl. Yeah, I saw that code, and wondered if there was a way around that n

Re: querying arbitrary variables via `port info --var`

2015-10-26 Thread Rainer Müller
On 2015-10-23 22:20, Ryan Schmidt wrote: > > On Oct 23, 2015, at 3:02 PM, René J.V. Bertin wrote: > >> I managed to extend the `port info` syntax so that it accepts `port >> info --var foo` but of course ran into the issue that lots of >> variables aren't known when the code is evaluated. >> >>