I should like to think that we should mimic other port systems --- what methods do they commonly have available?But what should 'port list' do in your opinion? We can try to fix theexisting command. But in its current form, it causes too much confusion.
For "port list" specifically, I would expect a listing of package names and package versions with an indication that it's out of date --- much like port outdated. I suggest we then throw in an additional third column indicating the status of that specific version. Here's an example:
xorg-xproto 7.0.14_1 < 7.0.15_0 (active) xorg-xproto 7.0.14_0 < 7.0.15_0 (inactive)You'll note that I demonstrate what I feel should happen if there's more than one port installed.
As for what's confusing, I feel we have too many commands available that overlap on naming. I think it would be a good idea to either consolidate or rename these functions. Since I'm talking about mimicking other port systems (for better or worse) I would expect "list" to provide the basic listings we provide from other functions as submethods:
list all list available list updates list installed list extras list obsoletes list recentI would expect the searching ability to included on all these (e.g., list updates foo*).
Feel free to throw more ideas onto this or pull some out; by no means should I be the only person driving MacPorts!
I happen to be familiar with yum: install, update, check-update,remove, list, info , provides, whatprovides, clean, makecache, search,shell, resolvedep, deplist, repolist, help Should we pick one system and go with it (or did we and I missed that memo)?I don't see a reason to tie ourself to a specific other system. We are getting new users coming from all different platforms. Would you expect MacPorts to have Super Cow Powers? ;-)
sudo apt-get moo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
