mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/7] ptxdist: Add local-src command
Date: Fri, 28 Feb 2014 15:47:16 +0100	[thread overview]
Message-ID: <20140228144716.GT6865@pengutronix.de> (raw)
In-Reply-To: <20140228140150.GE17250@pengutronix.de>

On Fri, Feb 28, 2014 at 03:01:50PM +0100, Sascha Hauer wrote:
> On Fri, Feb 28, 2014 at 02:48:20PM +0100, Alexander Dahl wrote:
> > Hei hei, 
> > 
> > Am 2014-02-26 15:13, schrieb Sascha Hauer:
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > ---
> > 
> > [snip]
> > 
> > > +  local-src <pkg> <directory>	overwrite a package source with a
> > > locally provided
> > > +				directory containing the sourcecode.
> > 
> > What exactly is the use case for this? Which source gets overwritten
> > with what other source and why?
> 
> You may be aware that you can put a link from local_src/${PACKAGE_NAME}_${PLATFORM}
> to a local directory. In this case ptxdist will use this directory as
> source directory for a package instead of the tarball. This is useful
> if you are working on the sourcecode for a package while compiling with
> ptxdist. The command is just a shortcut to create the link because I
> always forget the exact name of the link.
Obviously yes, it's local_src/${PACKAGE_NAME}.${PLATFORM} :-)

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-02-28 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 14:13 [ptxdist] [PATCH 1/7] ptxdist: Add list-packages command Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 2/7] ptxdist: Add local-src command Sascha Hauer
2014-02-28 13:48   ` Alexander Dahl
2014-02-28 14:01     ` Sascha Hauer
2014-02-28 14:47       ` Uwe Kleine-König [this message]
2014-02-28 14:58       ` Juergen Beisert
2014-02-28 15:54       ` Alexander Dahl
2014-02-26 14:13 ` [ptxdist] [PATCH 3/7] barebox: Add optional dependency to host-libusb Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 4/7] barebox: Only install defaultenv file if it exists Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 5/7] add ptxsudo alias to ptxdist bash Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 6/7] Add dfu-util rules for host Sascha Hauer
2014-02-26 14:13 ` [ptxdist] [PATCH 7/7] dfu-util: version bump to 0.7 Sascha Hauer
2014-02-26 16:30 ` [ptxdist] [PATCH 1/7] ptxdist: Add list-packages command Alexander Dahl
2014-02-27  8:48   ` Sascha Hauer
2014-03-06 17:52 ` 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=20140228144716.GT6865@pengutronix.de \
    --to=u.kleine-koenig@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