Marguerite Su (i@marguerite.su) wrote:
Hi, guys,
You are diving too deep that I can't quite follow even by reading the whole thread...
I just need some clearance:
Will this be (possibly) a RFC that appears on wiki and limits all packagers?
Sorry, I thought I answered that already but can't find my reply now. I think the goal is to clarify this page: http://en.opensuse.org/openSUSE:Package_naming_guidelines#Handling_special_v... Notice this page is a set of guidelines not rules. And the section we are talking about concerns SCM snapshots, not packaging of official release tarballs.
Or you were just talking about OBS coding/automatic packaging eg tar_scm backend
Yes, this is mainly about tar_scm, because it would be very tedious to assign timestamps and commit hashes / numbers by hand.
If it's a RFC, do our packagers need attending a codeschool tutorial before fetching from svn/git?
No, tar_scm makes it easy to do without knowing svn / git / hg / bzr.
You know, many of us just learned `svn co` and `git clone`...
And I see you talked the importance of "hashes", now I know by using it everything else is not needed.
In the git case, having hashes in the version string is very useful because it makes it easy to tell exactly which version of the git source the package came from. This is very important in debugging, for example.
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.
Or we just want users get the idea "wow it's from svn/git. wow it's a dev version"
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. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org