Mailing lists are what regrets are for.
Michael David Crawford, Baritone
mdcrawf...@gmail.com
One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.
On Tue, Feb 14, 2017 at 4:03 PM, bunk3m wrote:
> Hello all,
>
> My apologies for my mistaken post to the list yesterda.
>
Hello all,
My apologies for my mistaken post to the list yesterda.
Doh!
Too little sleep and to fast on the reply. Sorry.
B.
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
> 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
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
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/
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
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
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
> On Feb 10, 2017, at 3:11 PM, Lee Bast wrote:
>
> I've just been trying to do a new setup of a freshly installed system
> (macOS 10.12.3, Xcode 8.2.1) with MacPorts with just libressl and python
> installed so far, but cannot install openssh with libressl. I have verified
> this on two
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
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?
12 matches
Mail list logo
