public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: drobbins@gentoo.org
To: Justin Vander Ziel <zielot@thebestisp.com>
Subject: Re: [gentoo-dev] Bug report, Portage question, No sources included
Date: Sun, 7 Jan 2001 20:27:26 -0700	[thread overview]
Message-ID: <20010107202726.D7802@cvs.gentoo.org> (raw)
In-Reply-To: <001601c07915$96d21b80$0701a8c0@rayuela>; from zielot@thebestisp.com on Sun, Jan 07, 2001 at 07:51:58PM -0600

On Sun, Jan 07, 2001 at 07:51:58PM -0600, Justin Vander Ziel wrote:

> After having read through some comparisons of the various software management
> options here http://kitenet.net/~joey/pkg-comp/ , here
> http://vip.hpnc.com/~cbbrowne/linuxsysconfig.html and finally in the
> freshmeat article I feel like I have at least a general idea of where Portage
> is going. I have a couple of questions I am hoping someone in this list would
> answer for me * I have a slow dialup connection and I often download the
> software I need at work where I have a T1 and either carry it home on a
> Syquest 200Mb cartridge or burn a CD for myself there (which is how I got
> Gentoo in the first place). I'm not sure I am ever going to want to rsync my
> distro because I don't see a way of determining how long it's going to take
> without running an audit of my system. Any suggestions?  * What is the
> difference between Portage and e-build? Where does one begin and the other
> start? I'm familiar with Daniel's article that was posted on IBM about the
> e-build system (http://www-106.ibm.com/developerworks/library/bash3.html) *
> Perhaps I'm thinking in Microsoft mode here. My question is, is there an
> uninstall script ready now for ebuild? The autofs included with rc3 seems to
> be missing the pars_sun.so library file so I wanted to uninstall it and
> install the later version from the source code. I could list the files from
> the tbz2 file and do it by hand or I've even considered writing a script to
> do it for me but this seems to be a logical piece of the puzzle that is
> missing. (is that why this is called a beta release? B )

We do have a package uninstaller.  To use it, type:

# portage-unmerge net-misc/pkg-1.2.3-r5

You can also do this by typing:

# ebuild /path/to/version/exactly/matching/the/one/installed/foo.ebuild unmerge

Since we back up all installed ebuilds in /var/db/pkg, this will always work too:

# ebuild /var/db/pkg/net-misc/pkg-1.2.3-r5/pkg-1.2.3-r5.ebuild unmerge

As far as doing rsyncs, what I'd do is this.  Bring your Syquest to work, and
download the sources using rsync.  Then bring the Syquest home and rsync from
the Syquest to /usr/portage.  Then, continue to keep the Syquest up-to-date
by using rsync.  Let me know if you have any questions about how to do this.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			


       reply	other threads:[~2001-01-08  5:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001601c07915$96d21b80$0701a8c0@rayuela>
2001-01-08  3:27 ` drobbins [this message]
2001-01-08  3:32 ` [gentoo-dev] Bug report, Portage question, No sources included drobbins
2001-01-08  3:38 ` drobbins
2001-01-14 17:16 ` Achim Gottinger

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=20010107202726.D7802@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=zielot@thebestisp.com \
    /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