Thus spake Brian Elliott Finley ([EMAIL PROTECTED]):
Ok,
So I just took a look at the code sizes, after tarring and bzipping:
w/all source: 77m
w/all source, sans kernel: 41m
w/si source only: 4m
So, what I think we should do is:
1) Move download.systemimager.org to the systemimager.uchicago.edu
server (svn.sisuite.org). I'm working on this now.
Code moved over. DNS updated. Waiting for DNS propogation.
2) Whenever we update the version of a package in the build system,
copy that package up to:
download.systemimager.org:/pub/$package/$package.$version
I'll make sure we all have proper privileges to do this.
Done. If any of you have problems with permissions, let me or dann
know.
3) In the build system, point all of our URLs to our download
server, but have the upstream URL commented out just above, so
that someone can uncomment and use that if download.* is
unavailable for some reason.
Ie: #BC_URL := http://ftp.gnu.org/gnu/bc/$(BC_TARBALL)
BC_URL := http://download.systemimager.org/bc/$(BC_TARBALL)
This will ensure that we are making a copy of the source
available for at least 3 years. It will also have the side
effect of giving us some idea of how often people are building
from source, which could be interesting.
In progress.
4) Backup download.systemimager.org to our hard drives. ;-)
See and use ./tools/backup.systemimager.uchicago.edu The more of us
that use this on a regular basis, the more likely we are to have a
recent backup in case of a disaster.
5) When we do a release, only publish the systemimager-only source.
6) Add a README.package_maintainers file that says something like
this:
The standard SystemImager build process pulls source from our
download server. If you don't want it to do this when you do
your builds, you have two options:
1) Do a "make get_source" ahead of time, and copy the contents
of ./src/* and ./initrd_source/src/* to either /usr/src or
$HOME/src, and the build system will get the packages from
there instead of downloading them at build time.
2) Do a "make full_source_tarball". This will download all the
necessary source, and will create a single source tarball
that you can use for your build process.
Anyone care to comment or make any modifications to the above proposed
action?
-Brian
Thus spake Dann Frazier ([EMAIL PROTECTED]):
On Thu, 2005-12-15 at 00:17 -0600, Brian Elliott Finley wrote:
Devil's advocate comments below...
Thus spake efocht ([EMAIL PROTECTED]):
>Hi,
>
>I agree to Dann, can't see a legal issue here.
I'm not entirely sure Dann was saying there isn't a legal issue here,
but that the legal risks might be considered reasonable. However, I
can't tell if Dann is saying "go for it", "don't go for it", or "leave
me out of the decision." Dann?
I'm fine with whatever you guys want to do. Splitting out but still
deliverying all the 3rd party source sounds like a reasonable idea.
--
dann frazier <[EMAIL PROTECTED]>
--
Brian Elliott Finley
Mobile: 630.631.6621
--
Brian Elliott Finley
Mobile: 630.631.6621
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
