All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: bitbake-dev@lists.berlios.de,  openembedded-devel@lists.openembedded.org
Subject: Re: [Bitbake-dev] [PATCH] fetchers: Use tar --exclude pattern to remove SCM files
Date: Sun, 24 Oct 2010 21:56:44 +0200	[thread overview]
Message-ID: <4CC48F7C.2000403@freyther.de> (raw)
In-Reply-To: <AANLkTimjYwr6vn5Makva7yciDA2_4KoiM=K7EtQQkYCf@mail.gmail.com>

On 10/24/2010 08:35 PM, Khem Raj wrote:

>>
>> this is used in all efl recipes and I've noticed it in elementary only
>> because python-elementary depends on such new version.
> 
> Do you have a list of recipes which use this ? I am sure with git it
> will be hard to use such a thing
> as the git revs are random and simlarily many other SCMs


Speaking as upstream co-author of OpenBSC. We are using something like this to
get the revision from the last tag of the repository. If someone is doing a
make dist(check) we will copy a special version file into the tar.gz and use
that instead.

From an upstream point of view I think it is acceptable to say that the ones
that build stuff from a SCM (in contrast to a tarball) should have the files
of the SCM around...

PS: I liked the --exclude patch a lot too...



  reply	other threads:[~2010-10-24 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1285368419-12062-1-git-send-email-raj.khem@gmail.com>
2010-10-24  6:58 ` [Bitbake-dev] [PATCH] fetchers: Use tar --exclude pattern to remove SCM files Martin Jansa
2010-10-24  7:40   ` Khem Raj
2010-10-24  8:08     ` Martin Jansa
2010-10-24 18:35       ` Khem Raj
2010-10-24 19:56         ` Holger Freyther [this message]
2010-10-24 20:34           ` Chris Larson
2010-10-25 18:05             ` Khem Raj
2010-10-25  0:08           ` Khem Raj

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=4CC48F7C.2000403@freyther.de \
    --to=holger+oe@freyther.de \
    --cc=bitbake-dev@lists.berlios.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.