Marguerite Su (i@marguerite.su) wrote:
On Wed, Sep 11, 2013 at 3:39 AM, Adam Spiers <aspiers@suse.com> wrote:
But version number will be shown to all instead of just us...to most of the people (including me unluckily), hashes is just a random string at the very first glance.
Why is that a problem, and where? You mentioned before that it is shown in UIs, but the UI could easily hide the hash if it wanted to.
Yes...sorry, I think the situation that user-experience-concern guys and tech-detail-concern guys talking together loudly just make we misunderstand each other.
Yeah maybe :)
My original idea was that version number will be shown to users in YaST.
That's how it is currently - right?
So users seeing a random string will not get a clear view of what we just want to ship.
They can just judge by the svn/git prefix to get an idea that this version is a dev version.
Because a "random string" is meaningless if they don't know the tech details behind it.
But the "random string" is only the last part of the version string. The "normal" part would still be there. E.g. package-name-1.7.3+git.1378133004.9e149b8-11.1
Or we just want users get the idea "wow it's from svn/git. wow it's a dev version"
That might be useful to some users.
Most users except power users don't usually care much about the version number. A UI can choose how much or little of the $VERSION-$RELEASE string to expose. But usually it will make sense to expose either all of it, or none of it.
Yes...but they still want to know if they're installing a newer version or older version,
unless YaST can tell them by color diff.
eg, if you install fcitx-4.2.8.git20130911, you know it is newer than fcitx-4.2.8.git20130910
But if it is fcitx-4.2.8.git.aldjfad and fcitx-4.2.8.git.wueouqp, they just don't know what you are trying to telling them.
Exactly, and that's why I think it's important to have the date: package-name-1.7.3+git.1378133004.9e149b8-11.1 is obviously older than package-name-1.7.3+git.1378134719.8b662d0-6.1 Using an ISO format would make this even more obvious: package-name-1.7.3+git.20130902T154324.9e149b8-11.1 package-name-1.7.3+git.20130902T161159.8b662d0-6.1 But it's not just to make it clear for users. It's so that libzypp can tell, which is even more important.
My theory just comes from the fact that Arch linux changed all its network interfaces to random strings, eg: wlan0 is not wlan0, is wlanjlajl. So now users just know it's a wlan, they can't even search an answer through by Google because everyone's interface is now different.
None of these schemes suffer from this problem, because they still have the same "package-name-1.7.3" prefix. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org