From: "Raúl Sánchez Siles" <rasasi78@gmail.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 07:11:43 +0200 [thread overview]
Message-ID: <2228068.y4thvyPt1K@portaka> (raw)
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>
---
docs/manual/adding-packages-generic.txt | 2 ++
package/pkg-download.mk | 4 +++-
2 files changed, 5 insertions(+), 1 deletion(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Allow-svn-tags-and-branches-notation-in-PKG-_VERSION.patch
Type: text/x-patch
Size: 1350 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130918/e022a560/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130918/e022a560/attachment.asc>
next reply other threads:[~2013-09-18 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 5:11 Raúl Sánchez Siles [this message]
2013-09-18 17:20 ` [Buildroot] [PATCH 1/1] Allow svn tags and branches notation in $(PKG)_VERSION variable Thomas Petazzoni
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=2228068.y4thvyPt1K@portaka \
--to=rasasi78@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.