From: Jeff Smelser <tradergt@smelser.org>
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 14:12:04 -0600 [thread overview]
Message-ID: <200312071412.08154.tradergt@smelser.org> (raw)
In-Reply-To: <200312072059.53553.lafou@wanadoo.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 07 December 2003 01:59 pm, Philippe Lafoucrière wrote:
> 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...
Yes. but people like me would have a problem with that. So I would hope there
will be more of a generic routine on DB calls.. I don't care if I download a
sqlite db, but I don't want 4 copies either.. I would want a central db,
mysql such as, and have one copy of the portage db, and another table of
installed packages.. The table could be smart enough to know the machine
name, or separate tables wouldn't bother me much either.
Unless, I heard a rumor there was going to be more of a client/server version,
so maybe it can be solved that way?
I only keep one copy of /usr/portage now due to disk space. I refuse to tie
up that much disk space when I can centralize it.
- --
Speak softly and carry a cellular phone.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/04mXld4MRA3gEwYRAnvQAKDpXn7Oo7Gy8hSAKt125mOzTYXyzQCfS1Vu
Z+HDFOD1Gj3LzuDR0tp5djQ=
=pAur
-----END PGP SIGNATURE-----
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-12-07 20:12 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
2003-12-07 20:12 ` Jeff Smelser [this message]
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=200312071412.08154.tradergt@smelser.org \
--to=tradergt@smelser.org \
--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