All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] linux: xenomai: allow URL for the ADEOS/IPIPE patch
Date: Sun, 19 May 2019 11:17:07 +0200	[thread overview]
Message-ID: <20190519091707.GB4569@scaer> (raw)
In-Reply-To: <20190518220632.312f98da@windsurf>

Thomas, S?bastien, All,

On 2019-05-18 22:06 +0200, Thomas Petazzoni spake thusly:
> On Fri, 17 May 2019 14:50:49 +0200
> S?bastien Szymanski <sebastien.szymanski@armadeus.com> wrote:
> > diff --git a/linux/linux-ext-xenomai.mk b/linux/linux-ext-xenomai.mk
> > index d066bb32ac..ed29943e6c 100644
> > --- a/linux/linux-ext-xenomai.mk
> > +++ b/linux/linux-ext-xenomai.mk
> > @@ -8,10 +8,20 @@ LINUX_EXTENSIONS += xenomai
> >  
> >  # Adeos patch version
> >  XENOMAI_ADEOS_PATCH = $(call qstrip,$(BR2_LINUX_KERNEL_EXT_XENOMAI_ADEOS_PATCH))
> > +
> > +ifneq ($(filter ftp://% http://% https://%, $(XENOMAI_ADEOS_PATCH)),)
> > +XENOMAI_ADEOS_PATCH_NAME = $(notdir $(XENOMAI_ADEOS_PATCH))
> > +XENOMAI_ADEOS_PATCH_PATH = $(LINUX_DL_DIR)/$(XENOMAI_ADEOS_PATCH_NAME)
> > +LINUX_EXTRA_DOWNLOADS += $(XENOMAI_ADEOS_PATCH)
> > +BR_NO_CHECK_HASH_FOR += $(XENOMAI_ADEOS_PATCH_NAME)
> > +else
> > +XENOMAI_ADEOS_PATCH_PATH = $(subst file://,,$(XENOMAI_ADEOS_PATCH))
> 
> I don't feel super strongly about this, but everywhere else in
> Buildroot when paths are specified through configuration options, we do
> not support having a file:// URI. For example the
> BR2_LINUX_KERNEL_PATCH option will support file paths only without
> file://.
> 
> So for consistency, I would do the same here, and therefore just do:
> 
> XENOMAI_ADEOS_PATCH_PATH = $(XENOMAI_ADEOS_PATCH)
> 
> Yann, what do you think ?

Indeed, I don't see the point in the file:// scheme. I don't even see
people really using it routinely.

But as far as I can see, the above, although wrong, does not require
that the file:// prefix be used. If it is there, it is scrubbed;
otherwise the filename is used as-is.

And it is wrong, because it should only remove it at the beginning.
$(subst ...) would remove it anywhere. So if we were to use it (and I
think we should not), we'd have to use $(patsubst ...) instead;
    XENOMAI_ADEOS_PATCH_PATH = $(patsubst file://%,%,$(XENOMAI_ADEOS_PATCH))

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-05-19  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 12:50 [Buildroot] [PATCH v2 1/1] linux: xenomai: allow URL for the ADEOS/IPIPE patch Sébastien Szymanski
2019-05-18 20:06 ` Thomas Petazzoni
2019-05-19  9:17   ` Yann E. MORIN [this message]
2019-05-20  7:29     ` Sébastien Szymanski
2019-05-20  7:31       ` Thomas Petazzoni
2019-05-20  7:39         ` Sébastien Szymanski
2019-05-20 19:24 ` 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=20190519091707.GB4569@scaer \
    --to=yann.morin.1998@free.fr \
    --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.