Re: packaging issues: some serious, some not so serious

[Sam Ravnborg <sam@ravnborg.org>]

On Tue, Feb 19, 2008 at 05:15:10AM -0500, Robert P. J. Day wrote:
> On Tue, 19 Feb 2008, Sam Ravnborg wrote:
> 
> > On Tue, Feb 19, 2008 at 04:43:56AM -0500, Robert P. J. Day wrote:
> > > On Mon, 18 Feb 2008, Sam Ravnborg wrote:
> > >
> > > > 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
> > > > +
> > >
> > > would you not also need to include the regular files at the top of the
> > > source tree as well?  for some of the packaging targets, those files
> > > should be included as well.
> > Yes.
> > 'find --max-depth=1 *' or maybe we should provide a seperate list
> > for all the relevant filenmaes?
> 
> oh, dang ... it just occurred to me that it's still a good idea to add
> dirs like lost+found to the RCS_FIND_IGNORE and RCS_TAR_IGNORE
> variables since someone might, weirdly, decide to mount a subdirectory
> of the kernel source tree on a separate partition.  unlikely, yes, but
> it can happen.

If they do I would not care at all.
We should strive to make the normal cases behave as expected and try
to come up with general solutions that does not prevent the more
exotic cases.  But trying to imagine all the weird cases and handle
them will only result in an un-maintainable mess.

	Sam