Re: set port not to upgrade

2017-02-18 Thread db
> Really, MacPorts is designed for you to run the version of the ports that we > currently provide, not an earlier version. As I said, I do get your point. Nevertheless, I still think that something could be done. As of now I can locally duplicate a portfile, which has the effect of completely

Re: set port not to upgrade

2017-02-17 Thread Ryan Schmidt
On Feb 17, 2017, at 10:13, db wrote: > I get your point, but wouldn't a warning during build phase suffice? Be it a > leaf or node the port marked to not be upgraded. As of now, if port A, a > leaf, doesn't compile due to a bug in my system version, the only feasible > solution is to move the

Re: set port not to upgrade

2017-02-17 Thread db
I get your point, but wouldn't a warning during build phase suffice? Be it a leaf or node the port marked to not be upgraded. As of now, if port A, a leaf, doesn't compile due to a bug in my system version, the only feasible solution is to move the working Portfile to a local repo, or use a git

Re: set port not to upgrade

2017-02-16 Thread Ryan Schmidt
On Feb 15, 2017, at 15:58, Clemens Lang wrote: > On Wed, Feb 15, 2017 at 09:27:25AM +0100, db wrote: >> It is not, but a local portfile seems to also override a potential >> upgrade. >> >> Any other ways? Should I open a feature request? > > Not aware of any other ways. Feel free to open a tick

Re: set port not to upgrade

2017-02-15 Thread Clemens Lang
Hi, On Wed, Feb 15, 2017 at 09:27:25AM +0100, db wrote: > It is not, but a local portfile seems to also override a potential > upgrade. > > Any other ways? Should I open a feature request? Not aware of any other ways. Feel free to open a ticket, but please check for an existing one first. MacPo

Re: set port not to upgrade

2017-02-15 Thread db
On 14 Feb 2017, at 23:08, Clemens Lang wrote: > If this isn't sufficient, you can keep an old copy of the port in a local > portfile repository [1], but please don't forget about that if you do it. It is not, but a local portfile seems to also override a potential upgrade. Any other ways? Shoul

Re: set port not to upgrade

2017-02-14 Thread Clemens Lang
On Tue, Feb 14, 2017 at 12:03:21PM +0100, db wrote: > How can I mark a port to not be upgraded by `port upgrade outdated`, > for example, one that has a bug in my system version? 'outdated' will be default not include ports that have a newer version than the currently activated one installed (but

Re: set port not to upgrade

2017-02-14 Thread db
> You can try sudo port upgrade outdated and not Thanks, I have forgotten the syntax for that. I guess I could make an alias/function of it. > An even better feature would be a custom marking procedure that would allow a > user to “label” certain ports That would be ideal. Would it be feasibl

Re: set port not to upgrade

2017-02-14 Thread Carlo Tambuatco
An even better feature would be a custom marking procedure that would allow a user to “label” certain ports such as mysetofvideoports or mysetoftexteditors or whatever and then allow port actions to ignore or perform operations on just those sets. You could then create your own custom blacklist

Re: set port not to upgrade

2017-02-14 Thread Ralph Seichter
On 14.02.17 16:52, petr.2006 wrote: > On gentoo I prefer to modify /etc/portage/package.mask where I can > specify packages' versions which I do not want to upgrade. Masking is useful, of course, but there is a difference between not wanting to upgrade and not being able to upgrade due to a port/

Re: set port not to upgrade

2017-02-14 Thread petr.2006
On gentoo I prefer to modify /etc/portage/package.mask where I can specify packages' versions which I do not want to upgrade. > On 14 Feb 2017, at 16:30, Ralph Seichter wrote: > > On 14.02.2017 16:12, Richard L. Hamilton wrote: > >> Sure would be handy if one could optionally have ports that fa

Re: set port not to upgrade

2017-02-14 Thread Ralph Seichter
On 14.02.2017 16:12, Richard L. Hamilton wrote: > Sure would be handy if one could optionally have ports that failed to > upgrade blacklisted (for that version only), so that “port upgrade” > could still do everything else. Gentoo's "emerge" (https://wiki.gentoo.org/wiki/Portage#emerge) offers a

Re: set port not to upgrade

2017-02-14 Thread Richard L. Hamilton
Sure would be handy if one could optionally have ports that failed to upgrade blacklisted (for that version only), so that “port upgrade” could still do everything else. > On Feb 14, 2017, at 8:15 AM, Carlo Tambuatco wrote: > > You can try sudo port upgrade outdated and not > > or > > sudo

Re: set port not to upgrade

2017-02-14 Thread Carlo Tambuatco
You can try sudo port upgrade outdated and not or sudo port upgrade outdated and not and not rdependentof: (not sure of the exact syntax, here) To ignore a port and its recursive dependencies… > On Feb 14, 2017, at 6:03 AM, db wrote: > > How can I mark a port to not be upgraded by `po

set port not to upgrade

2017-02-14 Thread db
How can I mark a port to not be upgraded by `port upgrade outdated`, for example, one that has a bug in my system version?