From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] git ptxdist best practices
Date: Fri, 10 Jan 2014 16:37:43 +0100 [thread overview]
Message-ID: <20140110153743.GC20358@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjxObcyEYdDFA+piSWAqdv9Ha05AwQ9HioK142s3gVmjtw@mail.gmail.com>
On Thu, Jan 09, 2014 at 11:37:15AM -0500, Jon Ringle wrote:
> On Thu, Jan 9, 2014 at 11:06 AM, Michael Olbrich
> <m.olbrich@pengutronix.de>wrote:
>
> > On Thu, Jan 09, 2014 at 10:23:58AM -0500, Jon Ringle wrote:> One issue
> > that I ran across with this is that I have:
> > > PTXCONF_SETUP_PTXMIRROR_ONLY=y
> > > PTXCONF_SETUP_PTXMIRROR="http://opensource/pool/"
> > >
> > > Where opensource is an internal server that keeps all tar balls used to
> > > build. I'm paranoid that someday a upstream tar ball won't be available
> > and
> > > would cause a build break if someone tried to build and they didn't have
> > > that tar ball in ${PTXCONF_SETUP_SRCDIR}
> > >
> > > But for my purposes, if I wanted to use the git URL in a rule file I'd
> > want
> > > it to use the URL as is. But it rewrites it trying to use
> > > ${PTXCONF_SETUP_PTXMIRROR} instead in scripts/lib/ptxd_make_get.sh:295
> > >
> > > Is there away to work around this?
> >
> > put your git repositories in the mirror:
> > FOO_URL := http://opensource/pool/foo.git;tag=bar
> >
> > Unfortunately, I can't do that. The opensource server is under IT control
> and they've locked it down so that I can only write to it using scp or sftp
> and have no ssh shell access to it.
>
> The mechanism whitelists any URL starting with ${PTXCONF_SETUP_PTXMIRROR}
> >
>
> Would the following approach work:
>
> 1. In ptxdist/rules/post/ptxd_make_world_common.make add to world/env/impl:
> pkg_url_safe="$(call ptx/escape,$($(1)_URL_SAFE))"
>
> 2. In ptxdist/scripts/lib/ptxd_make_get.sh function ptxd_make_get
> change all occurances of:
> if [ -z "${PTXCONF_SETUP_PTXMIRROR_ONLY}" ]; then
> with something like:
> if [ -z "${PTXCONF_SETUP_PTXMIRROR_ONLY}" -o -n "${pkg_url_safe}" ];
> then
>
> Then in the rule file you can do:
> FOO_URL_SAFE := y
>
> So that you can whitelist a specific URL if PTXCONF_SETUP_PTXMIRROR_ONLY is
> set
Hmmm, this is not so nice. How about making PTXCONF_SETUP_PTXMIRROR a list?
Then you can add http://opensource/pool/ and your git server to the
'whitelist'.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-10 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:32 Jon Ringle
2014-01-08 5:56 ` Alexander Dahl
2014-01-08 6:12 ` Jon Ringle
2014-01-08 9:21 ` Alexander Dahl
2014-01-08 9:48 ` Alexander Dahl
2014-01-08 9:52 ` Jürgen Beisert
2014-01-08 17:56 ` Jon Ringle
2014-01-08 20:43 ` Alexander Dahl
2014-01-08 7:59 ` Jürgen Beisert
2014-01-08 14:14 ` Jon Ringle
2014-01-09 8:10 ` Jürgen Beisert
2014-01-09 9:03 ` Olbrich, Michael
2014-01-09 15:23 ` Jon Ringle
2014-01-09 16:06 ` Michael Olbrich
2014-01-09 16:37 ` Jon Ringle
2014-01-10 15:37 ` Michael Olbrich [this message]
2014-01-10 15:41 ` Jon Ringle
2014-01-11 1:47 ` Jon Ringle
2014-01-24 9:21 ` Michael Olbrich
2014-01-24 13:10 ` Jon Ringle
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=20140110153743.GC20358@pengutronix.de \
--to=m.olbrich@pengutronix.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