Allow svn tags and branches notation in $(PKG)_VERSION variable.
Get series with b4
b4 am 20130920062849.0a7ba5ce@skateVersions newest first
- v2 Latest1 patch 0 repliesNew
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | Allow svn tags and branches notation in $(PKG)_VERSION variable. | +0 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [Buildroot] [PATCH v2 0/1] Allow svn tags and branches notation in $(PKG)_VERSION variable.
Dear Ra?l S?nchez Siles,
Quoted 2 lines · Ra?l S?nchez Siles
I still consider the key point is being able to encode the revision into the
$(PKG)_SOURCE variable.
I guess you meant "the key point is being able to encode the revision into the $(PKG)_VERSION" variable. But I don't see why this is important or useful, so could you explain why you believe it is necessary?
For example, for Buildroot, doing:
LIBFOO2_VERSION = branches/featureA LIBFOO2_SITE = http://svn.happyserver.net/theproject
is not recommended at all, because you don't know which version of "featureA" you will be getting. One user may be fetching one revision, and if another user builds the same Buildroot configuration a few days later, it might be another revision with additional changes.
That's why you should instead use:
LIBFOO2_VERSION = <some revision number>LIBFOO2_SITE = http://svn.happyserver.net/theproject/branches/featureA
What is the problem with doing this?
Thanks!
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com