users confusing selfupdate and sync

[Emmanuel Hainry]

So, the present state is
sync only does some synchronization.
selfupdate updates port itself.
It seems clear enough to me.
Also, sync needs to be used far more often than selfupdate, so making
sync do the same as selfupdate would be overkill 90% of the time.
Finally, when people are advised to do "port sync", it is to solve a bug
in the porttree and in this case, sync is the right thing to do. If you
feel that users misunderstand sync for update, then a message as
suggested earlier would be the sane way of helping them.

Note that programs like firefox call "auto-update" the selfupdate
feature, and call sync the synchronization of data (bookmarks for
example).

Emmanuel

Citando Jeremy Lavergne :
> I've seen lots and lots of people suggesting the use of sync and never  
> realizing that they weren't upgrading MacPorts.  I've found it rather  
> frustrating because it does not seem to be getting better.
>
> Is there a way we can better document this or perhaps change the  
> functionality?
>
> We could slip an option into sync so that it does selfupdate unless you 
> pass it an argument (e.g., sync --portsonly).  This will not force users 
> to be re-educated and it will provide the benefit of ensuring people are 
> upgrading correctly.
>
> Thoughts?
>



> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev