From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Oscar Gomez Fuente <oscargomezf@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] Issues with SVN keywords and SITE_METHOD = svn
Date: Thu, 19 Aug 2021 22:13:44 +0200 [thread overview]
Message-ID: <20210819201344.GC27036@scaer> (raw)
In-Reply-To: <CALtfCQajW_ZAvVq3J5cA=XgSh1w6u9_Sv+VoRcqLkSMO46aghg@mail.gmail.com>
Oscar, All,
On 2021-08-19 20:26 +0200, Oscar Gomez Fuente spake thusly:
> I am updating my buildroot from 2020.08.2 to 2021.05.1 and I have
> found a problem.
>
> I have my own package created years ago with SITE_METHOD = svn. There
> are some files in that repository with keyword substitution that with
> buildroot 2020.08.2 works perfectly and the headers of the file is
> downloads from the repository perfectly, as you can see:
[--SNIP--]
> But with buildroot 2021.05.1 doesn't work fine:
[--SNIP--]
> I have check that my subversion is working propelrly in my computer,
> so I donot knoe what to do, to know this Rev keyword is very important
> for me due to the fact I use it for showing when I execute the
> program.
>
> Does anyone have any idea how to fix this issue?
As Vincent alerady replied, this was done intentionally, because keyword
substitution is dependent upon the settings at export/checkout:
different timezones and/or locales can yield different substitutions,
and this is thus not reproducible.
If knowing the revision is important in your package, you already have
it in the .mk, and so you could try a few things, like pass it at
configure time via a environment variable or via a file...
Altenatively, you could also decide to do the replacement on your own,
with a post-extract hook, something like:
$(SED) 's,$$Rev$$,$(FOO_VERSION),' $(shell grep -r -l -E '$$Rev$$' $(@D))
But this is not very robust, and keyword substitution is anyway a really
bad idea...
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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-19 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:26 [Buildroot] Issues with SVN keywords and SITE_METHOD = svn Oscar Gomez Fuente
2021-08-19 18:58 ` Vincent Fazio
2021-08-19 19:30 ` Oscar Gomez Fuente
2021-08-19 20:13 ` Yann E. MORIN [this message]
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=20210819201344.GC27036@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=oscargomezf@gmail.com \
/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