From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev source size
Date: Mon, 19 Jan 2004 19:51:16 +0000 [thread overview]
Message-ID: <20040119195116.GG3896@kroah.com> (raw)
In-Reply-To: <3931.212.67.81.238.1074502022.squirrel@webmail.hosting4p.com>
On Mon, Jan 19, 2004 at 08:40:44AM -0500, Martin Hicks wrote:
>
>
> On Mon, Jan 19, 2004 at 09:47:02AM +0100, Tomas wrote:
> > Binary size of udev is 50 KB, but source size is >2MB.
> > Is this necessary?
>
> It's due to the udev tarball including a whole whack of external stuff.
> I believe that Greg is doing this because many of these programs and
> libraries are very young, so compatibility changes from version to
> version.
>
> The tarball is currently carrying around libsysfs and klibc. The bulk
> of the extra space is klibc.
We also have a copy of a sysfs tree in order to run tests.
But the bulk of the tarball is probably the bitkeeper data. The tarball
contains all of the bitkeeper metadata so that anyone can see the entire
revision history.
Is it really a big deal that the tarball is the current size?
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-19 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 8:47 udev source size Tomas
2004-01-19 13:40 ` Martin Hicks
2004-01-19 19:51 ` Greg KH [this message]
2004-01-19 20:52 ` Martin Hicks
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=20040119195116.GG3896@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).