unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 14851@debbugs.gnu.org
Subject: bug#14851: linux-libre-3.3.8-gnu disappeared
Date: Fri, 19 Jul 2013 16:40:28 -0300	[thread overview]
Message-ID: <orfvvacp8z.fsf@livre.home> (raw)
In-Reply-To: <201307191851.47553.andreas@enge.fr> (Andreas Enge's message of "Fri, 19 Jul 2013 18:51:47 +0200")

On Jul 19, 2013, Andreas Enge <andreas@enge.fr> wrote:

> Am Freitag, 19. Juli 2013 schrieb Alexandre Oliva:
>> However, considering we put out multiple GBs of builds per
>> week, I don't think it's realistic to keep them all forever.  Not in our
>> own server, not at ftp.gnu.org.

> As far as I know, ftp.gnu.org would only be concerned with the source,

I don't know about that.  I've seen binaries in ftp.gnu.org in the past.
This should indeed reduce significantly the space requirements to a bit
less than 1GB per week, considering 4 releases per week in 3 different
compression formats.

OTOH, if we're to be strict, we should publish only the deblob scripts,
for those are the ultimate sources produced by the GNU Linux-libre
project.  The tarballs and diffs and deltas are just the result of
running those scripts on tarballs produced by third parties.

The scripts would be trivial to retain indefinitely; even more so
because they seldom change for stable releases.

> and these source tarballs are usually kept indefinitely.

> One also need not add the patch and diff files, so that the amount of 
> storage would be quite manageable.

The diff files are probably no big deal (10% increase, not an order of
magnitude like the build tarballs and debuginfo rpms).  Excluding them
would probably make for more work in the upload script, though.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

  reply	other threads:[~2013-07-19 19:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 11:02 bug#14851: linux-libre-3.3.8-gnu disappeared Andreas Enge
2013-07-12 22:30 ` Ludovic Courtès
2013-07-14  4:28   ` Jason Self
2013-07-14 13:55     ` Ludovic Courtès
2013-07-17 13:31     ` Ludovic Courtès
2013-07-19 11:08   ` Alexandre Oliva
2013-07-19 12:09     ` Ludovic Courtès
2013-07-19 19:50       ` Alexandre Oliva
2013-07-19 20:30         ` Ludovic Courtès
2013-07-19 16:51     ` Andreas Enge
2013-07-19 19:40       ` Alexandre Oliva [this message]
2017-04-03 10:53 ` bug#14851: #14851 - " ng0
2017-05-05 18:56   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=orfvvacp8z.fsf@livre.home \
    --to=lxoliva@fsfla.org \
    --cc=14851@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).