Hi, Ok, I get that.
Can we come up with a solution that works for you and for people that want to see all outdated ports they have installed easily? How about doing this? $ port live maintainer:cjones | uniq -f 1 Would that work for you? It prints only the first main port reports. Blair > On Aug 31, 2019, at 11:04 AM, Chris Jones <[email protected]> wrote: > > Hi, > > I use > > port live maintainer:cjones > > For that. For the py ports I maintain I do not want the above to give > multiple reports for each version supported. Hence the livecheck none for > these, so only the main stub port reports back. > > Chris > >> On 31 Aug 2019, at 7:02 pm, Blair Zajac <[email protected]> wrote: >> >> Yes, however, it’s not as convenient as seeing what ports you have that have >> new upstream versions. I would rather take more computing time and resources >> then my time manually doing `port livecheck py-virtualenv` and the other >> ones. My time is much more valuable than 4 times the number of HTTP requests. >> >> Blair >> >>> On Aug 31, 2019, at 10:57 AM, Chris Jones <[email protected]> wrote: >>> >>> It is intentional that the version specific py ports have livecheck none. >>> The idea is you don’t need every one of the versions performing the check, >>> only the non versioned port. >>> >>>> On 31 Aug 2019, at 5:50 pm, Blair Zajac <[email protected]> wrote: >>>> >>>> I care about such ports, e.g. py37-tensorflow and py37-virtualenv, so I >>>> would have that in requested. So that appears to not directly solve the >>>> issue. >>>> >>>>> On Aug 31, 2019, at 9:16 AM, Jeremy Lavergne <[email protected]> wrote: >>>>> >>>>> As an alternative or workaround, would narrowing to `port livecheck >>>>> requested` be useful for you? >>>>> >>>>> >>>>>> On 8/31/19 11:58 AM, Blair Zajac wrote: >>>>>> Hi all, >>>>>> It appears a number of ports, particularly py-* ports, use >>>>>> “livecheck.type none”. I find running ‘port livecheck installed’ a handy >>>>>> way to see if any of the ports I care about have an update, however, >>>>>> this doesn’t work for the py-* ones. >>>>>> Can something be changed to support this? Would the livecheck code need >>>>>> to specially handle the port name when ${name} is a py??-* variant? >>>>>> Blair >>>>> >>>> >>> >>> >> > >
