cvs commit: src/usr.sbin/pkg_install/info info.h main.c src/usr.sbin/pkg_install/libpkg_version.1

[Doug Barton]

Oliver Eikemeier wrote:
> David E. O'Brien wrote:
> 
>> obrien      2004-10-18 05:34:54 UTC
>>
>>   FreeBSD src repository
>>
>>   Modified files:
>>     usr.sbin/pkg_install/info info.h main.c
>>     usr.sbin/pkg_install/lib global.c lib.h
>>     usr.sbin/pkg_install/version main.c perform.c pkg_version.1
>>   Log:
>>   Add a -q flag to pkg_version.  It suppresses the output of <,=,>.
>>   This makes it possible to "portupgrade `pkg_version -q -l '<'`".
> 
> 
> You can always do "portupgrade -a" or "portupgrade `pkg_version -l '<' |
> awk '{print$1}'`". This will also work when "pkg_version -v" is used,
> while the current `pkg_version -qv' has a strange output. I can't see
> the real use of this flag, besides, where can I find portupdate(8)?

The argument that you can do 'portupgrade <anything>' to replace
functionality in the base is a total non-starter, since not only do many of
our users (including myself) not use it, but we shouldn't be making
decisions about the ports system based on _any_ optional component.
portupgrade is also not the only show in town, so we should be careful not
to stifle creativity in other areas.

I'm actually more sympathetic to your awk argument here, and in fact that's
what I was thinking about when I saw David's commit. However, I'm also
guilty of adding a feature to the original perl version of pkg_version that
could have been done with piped commands, so I have a hard time being
critical on this one. :)

Doug

-- 

	If you're never wrong, you're not trying hard enough