From: "Kevin Gordon" <kgordon@paradise.net.nz>
To: <gentoo-dev@cvs.gentoo.org>
Subject: [gentoo-dev] emerge with portage 1.6.7
Date: Sat Sep 8 20:28:02 2001 [thread overview]
Message-ID: <001501c138d7$34f1a3e0$0501010a@kgpro> (raw)
Hi everyone,
Help with these please:
(1) emerge --pretend parted-1.4.17.ebuild
error: could not find match for >=sys-devel/automake-1.4_p5
(2) emerge nautilus needs:
emerge librsvg-1.0.1.ebuild
fails at rsvg-ft.c (too fast to catch line!)
Can a bash buffer/screen be increased in size. I lose a lot off the
top.
(3) I am still using linux-2.4.1_pre8-r1. I have collected up to 3 copies of
increasing versions of applications and libraries in many areas. I guess I
can unmerge the older applications but the libraries I am not sure whether
to unmerge. I need a tidy up as more and more upgrades move in as
dependencies. What is the most practical approach?
Best Regards,
Kevin Gordon
next reply other threads:[~2001-09-09 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 20:28 Kevin Gordon [this message]
2001-09-09 6:24 ` [gentoo-dev] emerge with portage 1.6.7 Mikael Hallendal
2001-09-10 3:47 ` Kevin Gordon
2001-09-10 9:12 ` Mikael Hallendal
2001-09-11 3:30 ` Kevin Gordon
2001-09-11 6:39 ` Mikael Hallendal
2001-11-12 12:36 ` [gentoo-dev] smtp server mats pettersson
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='001501c138d7$34f1a3e0$0501010a@kgpro' \
--to=kgordon@paradise.net.nz \
--cc=gentoo-dev@cvs.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