From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Allow svn tags and branches notation in $(PKG)_VERSION variable.
Date: Wed, 18 Sep 2013 19:20:20 +0200 [thread overview]
Message-ID: <20130918192020.2ea7cb7e@skate> (raw)
In-Reply-To: <2228068.y4thvyPt1K@portaka>
Dear Ra?l S?nchez Siles,
On Wed, 18 Sep 2013 07:11:43 +0200, Ra?l S?nchez Siles wrote:
> According to user manual "generic-package Reference" section, LIBFOO_VERSION
> could refer to a branch or tag. This patch adds supports for this in the svn
> method case for the repositories following the branches/tags/trunk layout.
>
> Examples:
> LIBFOO_VERSION = tags/v3.2.1
> LIBFOO_SITE = svn://svn.server.net/myproject
>
> LIBFOO2_VERSION = branches/featureA
> LIBFOO2_SITE = http://svn.happyserver.net/theproject
> LIBFOO2_SITE_METHOD = svn
>
> Signed-off-by: Ra?l S?nchez Siles <rasasi78@gmail.com>
Hum, I am not sure. In the SVN world, a version is really a revision
number that you get with 'svn checkout -r'.
I believe to get a specific branch or tag with SVN, one should instead
use:
LIBFOO2_VERSION = <some revision number>
LIBFOO2_SITE = http://svn.happyserver.net/theproject/branches/featureA
I do understand the wish to make things 'like other VCS', but I am not
entirely convinced it's a good idea. But I can probably be convinced
with good arguments :)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-18 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 5:11 [Buildroot] [PATCH 1/1] Allow svn tags and branches notation in $(PKG)_VERSION variable Raúl Sánchez Siles
2013-09-18 17:20 ` Thomas Petazzoni [this message]
2013-09-19 19:20 ` Peter Korsgaard
2013-09-19 21:54 ` [Buildroot] [PATCH v2 " Raúl Sánchez Siles
2013-09-19 21:58 ` [Buildroot] [PATCH v2 0/1] " Raúl Sánchez Siles
2013-09-19 22:04 ` Raúl Sánchez Siles
2013-09-20 4:28 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130918192020.2ea7cb7e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox