svn commit: r407270 - head/ports-mgmt/portmaster

[Kubilay Kocak]

On 27/01/2016 7:42 PM, Alexey Dokuchaev wrote:
> On Wed, Jan 27, 2016 at 07:29:02PM +1100, Kubilay Kocak wrote:
>> On 27/01/2016 7:17 PM, Alexey Dokuchaev wrote:
>>> On Wed, Jan 27, 2016 at 06:40:46PM +1100, Kubilay Kocak wrote:
>>>> Given what the term 'deprecated' implies, I would use a pre-everything:
>>>> message instead.
>>>
>>> That's a good idea actually.
>>
>> 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.
> 
> Personally I don't think that DEPRECATED is *that* loaded.  IMHO it works
> quite fine for cases like this one, and no, it should not imply expiration
> date.  But perhaps there is warrant for CAUTION/ALERT/WARNING/INFORMATION
> or similar indeed.

Neither do I. However, while *we* might grok it's non-specific nature,
but I'll bet you $100 that the vast majority of software users (not just
of FreeBSD)  would go by the dictionary definition, or some equivalent
of it:

3. Computers: To mark (a component of a software standard) as obsolete
to warn against its use in the future so that it may be phased out.

DEPRECATED's non specific nature is kind of what I was getting at, and
why I think there's room for something better.

> ./danfe
>