From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Makefile: simplify target skeleton copying
Date: Thu, 28 Mar 2013 09:20:35 +0100 [thread overview]
Message-ID: <5153FD53.3050701@mind.be> (raw)
In-Reply-To: <CAAXf6LWWJMrJBvkf_jwMrrHT73dOy85_iQJpcZVbhF4SKcjjSw@mail.gmail.com>
On 28/03/13 09:13, Thomas De Schampheleire wrote:
> Hi,
>
>
> On Thu, Mar 28, 2013 at 9:07 AM, Peter Korsgaard <jacmet@sunsite.dk
> <mailto:jacmet@sunsite.dk>> wrote:
>
> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be
> <mailto:arnout@mind.be>> writes:
>
> Arnout> On 26/03/13 08:33, Peter Korsgaard wrote:
> >> + rsync -au --exclude=.empty --exclude=CVS --exclude=.svn
> --exclude='*~' \
> >> + $(TARGET_SKELETON)/ $(TARGET_DIR)/
>
> Arnout> Since TARGET_SKELETON can be configured to point to a git- or
> Arnout> mercurial-controlled directory, I'd want to exclude those
> as well. How
> Arnout> about the --cvs-exclude --include core that ThomasDS
> introduced?
>
> We can do that as well. I was a bit afraid of excluding files people
> wanted to keep, so I kept it how it was - But yes, like likelyhood is
> quite small.
>
> Care to send a patch to do this?
Yes, I care to send a patch, but if you look at my track record for
submitting infrastructural patches in the last couple of months, don't
hold your breath.
> Is this really needed?
> I was thinking about this as well, but later had the following reasoning
> (which could be wrong): for svn, if I recall correctly, there is a .svn
> in each subdirectory. This is not the case for .git or .hg (which only
> exist in the root of the repository). If one can assume that no-one puts
> the skeleton in a repository, the exclusion of .svn is enough.
I had one customer who put their overlay in a separate repository. (OK
in that particular case it was a subversion repository, but it _could_
have been a git/hg repository as well).
> Moreover, the --cvs-exclude option cannot be used in this case, as it
> also removes object files. In my version of rsync, this is the exclusion
> list used by --cvs-exclude:
>
> RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state .nse_depinfo
> *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej .del-* *.a *.olb *.o
> *.obj *.so *.exe *.Z *.elc *.ln core .svn/ .git/ .hg/ .bzr/
Ouch, that sucks.
How about:
- Create an rsync-filter file in the support directory;
- Create an RSYNC variable that has the option to use that file;
- Use the RSYNC variable everywhere instead of rsync;
- Document this;
- (optionally) add a Kconfig option to specify additional rsync filters.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-03-28 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 7:33 [Buildroot] [git commit] Makefile: simplify target skeleton copying Peter Korsgaard
2013-03-28 7:15 ` Arnout Vandecappelle
2013-03-28 8:07 ` Peter Korsgaard
2013-03-28 8:13 ` Thomas De Schampheleire
2013-03-28 8:20 ` Arnout Vandecappelle [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=5153FD53.3050701@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox