Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-osx
Navigation:
Lists: gentoo-osx: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-osx@g.o
From: Kito <kito@g.o>
Subject: Re: [PREFIX] Creating a profile (package.provided)
Date: Thu, 16 Mar 2006 11:11:42 -0600
On Mar 15, 2006, at 3:36 PM, m h wrote:

> So I tried using Kito's solaris configure code this morning.  I don't
> think it changed much.
>

First thing is the ${PREFIX}/etc/make.profile symlink is invalid,  
note the `!` .

> Here's my emerge --info:
> $ emerge  --info
> !!! Problem with sandbox binary. Disabling...
>
> !!! Relying on the shell to locate gcc, this may break
> !!! DISTCC, installing gcc-config and setting your current gcc
> !!! profile will fix this
> Portage 2.1.6 (!/home/spike/portage/portage-alt-prefix/profiles/ 
> linux/x86/fc3,
> gcc-3.4.3, unavailable, 2.6.9-5.EL i686)
> =================================================================
> System uname: 2.6.9-5.EL i686 i686
> Unknown Host Operating System
> dev-lang/python:     [Not Present]
> sys-apps/sandbox:    [Not Present]
> sys-devel/autoconf:  [Not Present]
> sys-devel/automake:  [Not Present]
> sys-devel/binutils:  [Not Present]
> sys-devel/libtool:   [Not Present]
> sys-devel/odcctools: [Not Present]
> virtual/os-headers:  [Not Present]
> ACCEPT_KEYWORDS="x86"
> AUTOCLEAN="yes"
> CBUILD="i686-pc-linux-gnu"
> CFLAGS="-O2 -mcpu=i686 -pipe"
> CHOST="i686-pc-linux-gnu"
> CONFIG_PROTECT="/etc /tmp/Mar15/etc /usr/kde/2/share/config
> /usr/kde/3/share/config /usr/share/config /var/qmail/control"
> CONFIG_PROTECT_MASK="/etc/gconf /tmp/Mar15/etc/env.d"
> CXXFLAGS="-O2 -mcpu=i686 -pipe"
> DISTDIR="/tmp/Mar15/usr/portage/distfiles"
> FEATURES="autoconfig distlocks metadata-transfer sfperms strict"
> GENTOO_MIRRORS="http://distfiles.gentoo.org
> http://distro.ibiblio.org/pub/linux/distributions/gentoo"
> LANG="en_US.UTF-8"
> PKGDIR="/tmp/Mar15/usr/portage/packages"
> PORTAGE_TMPDIR="/tmp/Mar15/var/tmp"
> PORTDIR="/tmp/Mar15/usr/portage"
> PREFIX="/tmp/Mar15"
> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
> USE="x86 berkdb crypt ipv6 ncurses nls pam perl python readline ssl
> tcpd zlib elibc_glibc kernel_linux userland_GNU"
> Unset:  ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL, LDFLAGS,
> LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
>
> I have a package.provided containing:
>
> dev-lang/python-2.3.4
> sys-devel/autoconf-2.59
> sys-devel/automake-1.9.2
> sys-devel/binutils-2.15.92
> sys-devel/libtools-1.5.6
>
> These are the rpm versions of these packages.  These versions aren't
> in the prefix portage tree.  What is the correct way to deal with
> these?
>

Provided packages don't necessarily need an existing ${PV} in the  
tree, so to start it is usually best to document which versions are  
actually available on the host as opposed to which versions are in  
PORTDIR. Take a look the 'packages' files in other profiles to see  
examples of excluding/including system packages to a profile and  
locking down specific versions.

Also, try the portage-prefix-2.1.10 snapshot, it adds the  
DEFAULT_PATH variable in make.globals, this allows you to set the  
PATH available to portage. It defaults to only ${PREFIX} paths, but  
it can be overridden in the profiles or make.conf.


--Kito




-- 
gentoo-osx@g.o mailing list


Replies:
Re: [PREFIX] Creating a profile (package.provided)
-- m h
References:
[PREFIX] Creating a profile (package.provided)
-- m h
Navigation:
Lists: gentoo-osx: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [PREFIX] Creating a profile (package.provided)
Next by thread:
Re: [PREFIX] Creating a profile (package.provided)
Previous by date:
Re: [PREFIX] Creating a profile (package.provided)
Next by date:
Re: [PREFIX] Creating a profile (package.provided)


Updated Jun 17, 2009

Summary: Archive of the gentoo-osx mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.