-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2010 01:45:26, Randal L. Schwartz wrote:
Adam == Adam Vande More amvandem...@gmail.com writes:
Adam Can you attach your make.conf?
WITHOUT_X11=yes
# added by use.perl 2010-02-28 17:41:39
PERL_VERSION=5.10.1
The problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2010 01:40:55, Randal L. Schwartz wrote:
I'd like the entire portage system to consider 5.8 to be dead, both
^^^
That's a gentoo-ism
for building from ports, and for installing packages that
Matthew == Matthew Seaman m.sea...@infracaninophile.co.uk writes:
Matthew For best results, install from ports rather than packages. If it's
Matthew pure-perl code, then this should be hardly more onerous than installing
Matthew a compiled package. XS code however will chew up some CPU cycles.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2010 17:21:48, Randal L. Schwartz wrote:
Matthew == Matthew Seaman m.sea...@infracaninophile.co.uk writes:
Matthew For best results, install from ports rather than packages. If it's
Matthew pure-perl code, then this should be hardly
On Mon, Mar 1, 2010 at 12:19 PM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
As far as I know, there isn't an official way to do this. What you
want sounds like a useful addition to the base system to me.
You could do it in a fairly gross hacky way, like the following. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2010 18:19:36, Matthew Seaman wrote:
On second thoughts, writing a small wrapper around pkg_add(1) that greps
through the @pkgdep lines in the +CONTENTS file from the package tarball
and bails if it finds the wrong version of perl would be
I've upgraded to Perl 5.10, but when I tried to install a few
things that depended on perl, the package installed perl5.8, because
that must be what it was compiled with.
How do I tell the ports system that perl5.8 should *never* be used, and rather
than install a package that needs it, I can
On Sun, Feb 28, 2010 at 2:51 PM, Randal L. Schwartz
mer...@stonehenge.comwrote:
I've upgraded to Perl 5.10, but when I tried to install a few
things that depended on perl, the package installed perl5.8, because
that must be what it was compiled with.
How do I tell the ports system that
Adam == Adam Vande More amvandem...@gmail.com writes:
Adam See /usr/ports/UPDATING and /etc/make.conf
Doesn't help. Packages that are compiled against 5.8 still want
to install 5.8.
I want this to fatal out, so I know to build from port, not use package.
portinstall -Pc MUMBLE is just too
On Sun, Feb 28, 2010 at 3:53 PM, Randal L. Schwartz
mer...@stonehenge.comwrote:
Adam == Adam Vande More amvandem...@gmail.com writes:
Adam See /usr/ports/UPDATING and /etc/make.conf
Doesn't help. Packages that are compiled against 5.8 still want
to install 5.8.
I want this to fatal out,
Adam == Adam Vande More amvandem...@gmail.com writes:
Adam If it completed successly it has to help. What are the result of each
step
Adam so we can isolate the problem.
It completes by installing 5.8. I'd like to prevent that.
I'd like the entire portage system to consider 5.8 to be dead,
It completes by installing 5.8. I'd like to prevent that.
I'd like the entire portage system to consider 5.8 to be dead, both
for building from ports, and for installing packages that say they
depend on that.
How do I get there?
Can you attach your make.conf?
--
Adam Vande More
Adam == Adam Vande More amvandem...@gmail.com writes:
Adam Can you attach your make.conf?
WITHOUT_X11=yes
# added by use.perl 2010-02-28 17:41:39
PERL_VERSION=5.10.1
The problem is not ports, it's packages. If a package specifies 5.8,
it installs the 5.8 package, and I'm toast.
13 matches
Mail list logo
