Ciaran McCreesh wrote:
Incidentally, I suspect the gcc example with _p is confusing people. The
normal use for an -scm suffix will be as follows:
Yeah I abused the _p suffix. My bad.
The whole _p thing only comes up for those very rare (or possibly
non-existent) projects that have patchset branches that are themselves
live.
Actually I was thinking local patchset level. Using a date was silly
though. What I'm doing with gcc locally is currently more like:
gcc-4.2.3_pre20071210_p2
(_preDATE is used solely due to restrictions of toolchain.eclass)
Basically I want to force an update
- when the ebuild is edited (_pre)
- when the patchset is updated (_p)
This naming is pretty much the same as the snapshot ebuilds in
the toolchain overlay, so an -scm suffix to indicate that these
are indeed live SVN ebuilds would be welcome.
I hope this clears up what I meant, to give an example of why one
might want to use version numbers with an -scm suffix.
--
looks like christmas at fifty-five degrees
this latitude weakens my knees
EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 (0xF9A40662)
--
[EMAIL PROTECTED] mailing list
