public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom St Denis <tom@securescience.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Idea for the portage maintainers
Date: Mon, 12 Apr 2004 08:03:13 -0400	[thread overview]
Message-ID: <200404120803.16933.tom@securescience.net> (raw)
In-Reply-To: <200404121245.25460.arutha@gmx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On April 12, 2004 06:45 am, Alexander Gretencord wrote:
> On Sunday 11 April 2004 13:55, Tom St Denis wrote:
> > I think a cool function [which I didn't see in the latest portage
> > release] is a "snapshot" and restore set of functionality.  e.g. you can
> > snapshot the current install set and later restore (by adding/removing
> > packages) as required.
>
> What exactly do you mean by that? What irritates me is that "by
> adding/removing packages". If you just want a list of all installed
> packages you can already get it. What I'd understand by snapshotting is
> really packaging a set of packages and their deps. Kind of a '-b' but after
> merging.

Well Ideally a command that simply emits a list of installed packages is what 
I'm talking about.  But specifically, it emits the list [and say GZIPs it at 
the same time] into a db of "restore points".  

So as another poster said I could do say 

emerge restore "11/04/04"

If I installed something today that I didn't like.  The trick is to make this 
painless for the user so the user won't scream in horror and go install 
Windows.

> > Also any plans to optimize the portage files?  80k small files amounts to
> > huge waste of space.
>
> Depends on your filesystem. With certain filesystems you could adjust the
> blocksize for /usr/portage/ to a smaller value (with a larger value
> for /usr/portage/distfiles of course) or use reiserfs with tail packing on.

Oh, ok so I'll just format my disk, reinstall Gentoo from scratch so that I 
can not waste 200M of space on 80k small files.

That's not really user friendly.  Could have done a JAR like setup for each 
dir of the tree.  e.g. all of app-text be one huge ZIP file [with no 
compression].  Such a setup might be a little slower to add/remove files but 
would waste less space.

The idea would make a little sense though in practice.  When I do "emerge 
sync" instead of fetching 1000s of small files I just check the timestamp on 
the directory zips and download them wholesale.  [Ok so maybe compression 
makes sense here].

That way as a user I don't have to worry about inserting/deleting files from a 
zip [which would take a while] only the server has todo it.  In fact the 
server could still use the "many files" approach and just zip on the fly when 
a user syncs.

I know that would make things a bit more complicated since mirrors update via 
"sync" as well.  I guess you could just have two types of portage trees.  
e.g. "packaged" and "straight" or something like that.  End users would use 
the "packaged" type [e.g. zip per category] and mirrors would use straight 
[e.g. all 80k files].

Anyways, I'm just throwing out ideas here.  Using the zip approach makes sense 
for end users.  First, it makes for faster syncing [less smaller files means 
fewer metadata commands] and wastes much less space [and would be faster 
since the kernel could cache it quicker!].

Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAeoWDsP+tEsHHY0ARAg/dAJwMV7cUdGl8GJ/qA0StH9RFwRajCACfWqL4
hv++FVTFxDrzXKCKrrN1s4Y=
=wEEo
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-04-12 12:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-11 11:55 [gentoo-dev] Idea for the portage maintainers Tom St Denis
2004-04-12 10:45 ` Alexander Gretencord
2004-04-12 12:03   ` Tom St Denis [this message]
2004-04-12 12:23     ` Georgi Georgiev
2004-04-12 12:36       ` Tom St Denis
2004-04-12 14:18         ` N. Owen Gunden
2004-04-12 15:12         ` Troy Dack
2004-04-12 15:15           ` Jason Stubbs
2004-04-12 16:22           ` Andrew Gaffney
2004-04-12 16:23             ` Todd Berman
2004-04-12 16:59               ` Andrew Gaffney
2004-04-12 17:03                 ` Todd Berman
2004-04-12 17:17                   ` Andrew Gaffney
2004-04-12 17:39                     ` Todd Berman
2004-04-13  1:04                       ` Jason Stubbs
2004-04-13  3:35                         ` Todd Berman
2004-04-13 15:39                   ` [gentoo-dev] Idea for the portage maintainers - personal experiences with a .zip-db Karl Trygve Kalleberg
2004-04-12 17:09                 ` [gentoo-dev] Idea for the portage maintainers Tom St Denis
2004-04-12 17:19                   ` Norberto Bensa
2004-04-12 17:21                     ` Tom St Denis
2004-04-13 12:18     ` Chris Bainbridge
2004-04-13 16:12       ` Chris Bainbridge
2004-04-12 11:57 ` Senor Rodgman
  -- strict thread matches above, loose matches on Subject: below --
2004-04-12 12:46 brettholcomb
2004-04-12 12:59 ` Tom St Denis
2004-04-12 19:55   ` Marius Mauch
2004-04-12 17:39 brettholcomb
2004-04-12 17:51 ` Andrew Gaffney
2004-04-12 20:00   ` Marius Mauch
2004-04-12 20:31     ` Marius Mauch
2004-04-12 20:46     ` Stuart Herbert
2004-04-12 20:58       ` Marius Mauch
2004-04-12 21:17         ` Stuart Herbert
2004-04-12 21:26           ` Spider
2004-04-12 23:44             ` Drake Wyrm
2004-04-12 21:26           ` Marius Mauch
2004-04-12 22:20             ` Stuart Herbert
2004-04-12 22:18               ` Andrew Gaffney
2004-04-12 22:38                 ` Stuart Herbert
2004-04-12 22:32               ` Marius Mauch
2004-04-12 22:44             ` Marius Mauch

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=200404120803.16933.tom@securescience.net \
    --to=tom@securescience.net \
    --cc=gentoo-dev@lists.gentoo.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