From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Cc: Pedro Lafuente <pedro.lafuente@avt-stoye.de>
Subject: Re: [ptxdist] get SVN folder ( without .tar extension)
Date: Fri, 7 Apr 2017 11:28:34 +0200 [thread overview]
Message-ID: <CABDcava4NKOA46ujh6nG=DhCk62FA59-Hr7nWuX=PAYRkps_GA@mail.gmail.com> (raw)
In-Reply-To: <cda2c57d-2343-305f-e1b8-7f484a1cc592@rohieb.name>
2017-04-06 13:55 GMT+02:00 Roland Hieber <rohieb@rohieb.name>:
> PACKAGES-$(PTXCONF_YOURPACKAGE) += yourpackage
> YOURPACKAGE_URL = svn://your-server/your-repostitory;ref=20
>
> (Unfortunately, I can't test it, I didn't find any SVN repos on the web)
>
> In the background, ptxdist will clone the repository, update to the
> specified revision, and still build a tarball out of it, so the next
> build steps are transparent.
Please be aware that versions of ptxdist before the just released
2017.04 have a problem when using SVN URLs and .tar.gz archives (the
generated .tar.gz archive would have a different MD5 sum each time).
To solve this, either upgrade to 2017.04 (where this issue is fixed)
or use a different archive format such as tar.bz2
Guillermo
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-04-07 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 22:12 [ptxdist] [PATCH] ppp: version bump 2.4.5 -> 2.4.7 Ladislav Michl
2017-04-06 9:26 ` [ptxdist] get SVN folder ( without .tar extension) Pedro Lafuente
2017-04-06 11:55 ` Roland Hieber
2017-04-06 12:01 ` Roland Hieber
2017-04-07 9:28 ` Guillermo Rodriguez Garcia [this message]
2017-04-12 20:30 ` [ptxdist] [PATCH v2] ppp: version bump 2.4.5 -> 2.4.7 Ladislav Michl
2017-04-21 13:02 ` Michael Olbrich
2017-04-21 14:11 ` Ladislav Michl
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='CABDcava4NKOA46ujh6nG=DhCk62FA59-Hr7nWuX=PAYRkps_GA@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=pedro.lafuente@avt-stoye.de \
--cc=ptxdist@pengutronix.de \
/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