public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page
Date: Sun, 7 Dec 2003 21:10:42 +0100	[thread overview]
Message-ID: <200312072110.42657.lafou@wanadoo.fr> (raw)
In-Reply-To: <200312072059.53553.lafou@wanadoo.fr>


> If you use a backend db using sqllite, you just have 1 file representing
> your DB, and so, your portage tree. Then you can send this file through
> rsync. Another DB file should be used to manage installed package. an
> emerge -UDp world should just look in the installed DB for packages, and
> then compare status in portage db. Maybe an idea...

I'm not sure every body has understand this :(

I just wonder why the tree has to be build on the cliend side. Official tree 
should be built on gentoo servers, and should be updated when new ebuilds are 
available in the tree.

this will be part of the python/twisted/sqlite prototype I'll start tomorrow 
(with Jason Mobarak, who proposed himself to help !).

--
Philippe


--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2003-12-07 20:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  9:58 [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-05 12:26 ` Paul de Vrieze
2003-12-05 21:33   ` George Shapovalov
2003-12-06 14:26     ` Paul de Vrieze
2003-12-06 19:35       ` Daniel Robbins
2003-12-06 19:41         ` Jon Portnoy
2003-12-07  0:13           ` [gentoo-portage-dev] ebuild strengths/weaknesses Daniel Robbins
2003-12-07  1:44           ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page Jason Stubbs
2003-12-07  2:39             ` George Shapovalov
2003-12-07  3:12               ` Jason Stubbs
2003-12-07  4:50               ` Ray Russell Reese III
2003-12-07  7:27                 ` Daniel Robbins
2003-12-07  7:40               ` Daniel Robbins
2003-12-07  9:11                 ` Kapil Thangavelu
2003-12-07 11:11                   ` Paul de Vrieze
2003-12-08 16:03                 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page, ebuild conversion Sandy McArthur
2003-12-07 11:05         ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page Paul de Vrieze
2003-12-07 19:59         ` Philippe Lafoucrière
2003-12-07 20:10           ` Philippe Lafoucrière [this message]
2003-12-07 20:12           ` Jeff Smelser
2003-12-07 21:01             ` [gentoo-portage-dev] gpg signing of Manifests Douglas Russell
2003-12-07 21:53               ` Douglas Russell
2003-12-06 23:00       ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-07 11:18         ` Paul de Vrieze
2003-12-05 16:54 ` [gentoo-portage-dev] portage-ng design competition -- not yet Daniel Robbins
2003-12-05 20:35   ` George Shapovalov
2003-12-05 21:59   ` [gentoo-portage-dev] portage-ng wish list Sandy McArthur

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=200312072110.42657.lafou@wanadoo.fr \
    --to=lafou@wanadoo.fr \
    --cc=gentoo-portage-dev@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