Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Jan 2016 20:10:21 +1100
From:      Kubilay Kocak <>
To:        Colin Percival <>
Cc:, "" <>, "" <>
Subject:   Re: svn commit: r407270 - head/ports-mgmt/portmaster
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 27/01/2016 7:58 PM, Colin Percival wrote:
> On 01/27/16 00:29, Kubilay Kocak wrote:
>> It would be nice to have something framework'ey that is less loaded than
>> DEPRECATED, but more specific and consistent than your standard ECHO_MSG
>> or pkg-message. Like CAUTION/ALERT/WARNING/INFORMATIONAL or similar.
> How about this?

That's a good start, but not the same as what I intended.

A WARNING/ALERT ability in the framework, independent to whether or not
those should be used for unmaintained ports.

I personally wouldn't use them for all unmaintained ports, because each
case is different, but the framework bits are valuable nonetheless.

But that aside, for example, I need/want to add "WARNINGS" to py-pip
(not to use pip to install python packages into the system python
package directory).

I want to add ALERTS to lang/python* ports that some standard library
functionality are availabe in separate ports.

There are many classes of things we could use this for.

If you don't mind, I'd like to rephrase the summary of that issue,
because I think tracking the desire for a feature is a good thing.

Want to link to this message? Use this URL: <>