public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: Re: packaging issues:  some serious, some not so serious
Date: Mon, 18 Feb 2008 13:20:00 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802181319160.4194@localhost.localdomain> (raw)
In-Reply-To: <20080218181747.GA23691@uranus.ravnborg.org>

On Mon, 18 Feb 2008, Sam Ravnborg wrote:

> I would much rather you persuaded your earlier idea list all the
> directories to visit. This list is known and easy to maintain
> whereas a blacklist like we have now only will grow bigger over
> time.
>
> We could add something like:
> diff --git a/Makefile b/Makefile
> index 0d585c0..fb5bbc3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -358,6 +358,11 @@ export MODVERDIR := $(if $(KBUILD_EXTMOD),$(firstword $(KBU
>  RCS_FIND_IGNORE := \( -name SCCS -o -name BitKeeper -o -name .svn -o -name CVS
>  export RCS_TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn --ex
>
> +# all dirs
> +KBUILD_ALL_DIRS := arch block crypto Documentation drivers fs include init
> +KBUILD_ALL_DIRS += ipc net samples scripts security sound usr virt
> +export KBUILD_ALL_DIRS
> +
>  # ===========================================================================
>  # Rules shared between *config targets and build targets
>
>
> And then use this definition in all find / tar operations.
> We do not need to change everything in one go as the old RCS_TAR_IGNORE
> and RCS_FIND_IGNORE can continue as is for a while.
>
> Can you please try out this approach?

sure, i prefer that strategy anyway.  let me work on it.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

  reply	other threads:[~2008-02-18 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 16:35 packaging issues: some serious, some not so serious Robert P. J. Day
2008-02-18 18:17 ` Sam Ravnborg
2008-02-18 18:20   ` Robert P. J. Day [this message]
2008-02-19  9:43   ` Robert P. J. Day
2008-02-19  9:52     ` Sam Ravnborg
2008-02-19 10:15       ` Robert P. J. Day
2008-02-19 11:49         ` Sam Ravnborg
2008-02-19 12:25           ` Robert P. J. Day
2008-02-19 13:13             ` Sam Ravnborg

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=alpine.LFD.1.00.0802181319160.4194@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox