From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] AT91bootstrap with ptxdist
Date: Mon, 29 Aug 2016 09:26:25 +0200 [thread overview]
Message-ID: <CABDcavbs-rod1mYqAEqVxsTck4SzET7RVZyw3psfueRAJsda=w@mail.gmail.com> (raw)
In-Reply-To: <CABDcavb6FUghro001aM+YOPY_X5mzN1A48w+TLTa91-4o5fJrw@mail.gmail.com>
Hello,
2016-08-25 13:15 GMT+02:00 Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com>:
> Hi Michael,
>
> 2016-08-25 12:54 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
>> On Mon, Aug 22, 2016 at 04:41:52PM +0200, Guillermo Rodriguez Garcia wrote:
>>> Hello all,
>>>
>>> I am trying to compile AT91bootstrap with ptxdist and I have found the
>>> following minor issues:
>>>
>>> 1. Starting from end of 2014, at91bootstrap releases are no longer
>>> published on ftp://www.at91.com/pub/.. The "official" source now seems
>>> to be the at91bootstrap repo. The ftp site contains versions up to
>>> 3.7.1 (Nov 2014), while the github repo contains versions from 3.7
>>> (Sep 2014) onwards.
>>>
>>> I can just send a patch to update the URL but that would break if
>>> someone wants to use an old at91bootstrap version. How should this be
>>> handled?
>>
>> There can be multiple URLs. PTXdist will try one after the other until one
>> works. So just add another URL.
>
> Didn't know that, thank you.
>
> In this case however there's another complication which is the file suffix.
> For the 'old' ftp url, tar.bz2 is used. For the new one (github) you
> can get .zip or .tar.gz. This means it is not only the URL that
> changes, but also the name of the downloaded file. How can this be
> handled?
Any thoughts on this? How can we handle the case where the suffix may
be different depending on the URL used?
If I understand correctly, @packagename@_SOURCE must be defined with
the current filename for the get and extract stages. But the actual
filename depends on which URL was used. Is there a way to define this
dynamically?
An alternative approach would be to add a new config option to
at91bootstrap2.in, e.g. AT91BOOTSTRAP2_LEGACY -- if set, use the old
ftp URL (which is not being updated anymore). If unset, use the new
github URL. Is this acceptable ?
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-08-29 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 14:41 Guillermo Rodriguez Garcia
2016-08-25 10:54 ` Michael Olbrich
2016-08-25 11:15 ` Guillermo Rodriguez Garcia
2016-08-29 7:26 ` Guillermo Rodriguez Garcia [this message]
2016-08-30 7:19 ` Guillermo Rodriguez Garcia
2016-08-30 8:34 ` [ptxdist] [PATCH] Update at91bootstrap2 package for compatibility with 3.x series Guillermo Rodriguez
2016-09-02 11:53 ` [ptxdist] AT91bootstrap with ptxdist Michael Olbrich
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='CABDcavbs-rod1mYqAEqVxsTck4SzET7RVZyw3psfueRAJsda=w@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--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