All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, rmoser <mlmoser@comcast.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel source tree splitting
Date: Thu, 01 May 2003 02:14:10 -0400	[thread overview]
Message-ID: <3EB0BB32.1070500@wmich.edu> (raw)
In-Reply-To: <9930000.1051762204@[10.10.2.4]>

Martin J. Bligh wrote:
>>I'm probably misreading this...but,
>>
>>Have you tried this yet?  Does it modify/customize all Kconfig
>>and Makefiles for the selected tree splits?
>>
>>A few days ago, in one tree, I rm-ed arch/{all that I don't need}
>>and drivers/{all that I don't need}.
>>After that I couldn't run "make *config" because it wants all of
>>those files, even if I don't want them.
>>
>>So there are many edits that needed to be done in lots of
>>Kconfig and Makefiles if one selectively pulls or omits certain
>>sub-directories.
> 
> 
> Indeed, I ran across the same thing a while back. Would be *really* nice to
> fix, if only so some poor sod over a modem can download a smaller tarball,
> or save some diskspace.
> 
> M.
> 

Tried doing this a while ago with my own cvs server. I'd download the 
tarball untar it into the cvs dump. I made a modules file tha that 
described all kinds of possible modules and then modules that utilized 
those and so on until you could just do co -z9 linux-i386 to get a all 
the files required to make any i386 linux ...it was mostly to just 
separate the archs, not unneeded drivers. Of course i quickly ran into 
the make not working without all the other files from the other archs 
and i came to the conclusion you couldn't do this without editing 
certain build scripts and files (and since I didn't want the files to be 
altered in case people would eventually want to call security into 
question) i killed the whole idea.

This idea comes and goes like many others.  As far as modular 
programming goes the kernel isn't written to be very modular, either 
that or it is and the build system just looks over that fact.  It would 
be interesting to see how hard it would be to have the current config to 
not only generate its .config but also a list of commands that an 
autoconf created ./configure can read and use to generate the makefiles 
we then use to build the kernel.  it could also help in enforcing 
minimum versions instead of hoping the user does it before complaining 
to people who could be doing better things with their time.  Anyways, 
i'm sure this idea has been coined and dropped before as well.  So it's 
back to the way things are done like normal.


  reply	other threads:[~2003-05-01  6:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 23:46 Kernel source tree splitting rmoser
2003-05-01  0:21 ` Randy.Dunlap
2003-05-01  0:44   ` rmoser
2003-05-01  2:51     ` Randy.Dunlap
2003-05-01 10:13       ` rmoser
2003-05-01  0:52   ` Larry McVoy
2003-05-01  1:00     ` rmoser
2003-05-01 17:28     ` James H. Cloos Jr.
2003-05-01  4:10   ` Martin J. Bligh
2003-05-01  6:14     ` Ed Sweetman [this message]
2003-05-01  6:14       ` Peter Riocreux
2003-05-02  0:09   ` Randy.Dunlap
2003-05-02  0:41     ` rmoser
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 11:54 Chuck Ebbert
2003-05-01 14:06 ` Martin J. Bligh
2003-05-01 14:20   ` Willy TARREAU
2003-05-01 14:35     ` Martin J. Bligh
2003-05-01 14:43       ` Willy TARREAU
2003-05-01 15:01       ` Larry McVoy
2003-05-01 15:11         ` Martin J. Bligh
2003-05-01 17:22 ` Balram Adlakha
2003-05-01 17:28   ` Ben Greear
2003-05-01 20:03     ` John Bradford
2003-05-01 16:00 Chuck Ebbert

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=3EB0BB32.1070500@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mlmoser@comcast.net \
    --cc=rddunlap@osdl.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.