| 1 |
On Mon, 2006-08-07 at 09:52 -0500, Andrew Gaffney wrote: |
| 2 |
> Edward Catmur wrote: |
| 3 |
> > Is it possible to get Portage (or ebuild) to build a package for |
| 4 |
> > installation into /opt? If not, how much work would that be? |
| 5 |
> > |
| 6 |
> > What would be great would be to have emerge --optinstall package, that |
| 7 |
> > installs the package into /opt/$PV and doesn't create a vdb entry... |
| 8 |
> > feasible? |
| 9 |
> |
| 10 |
> Possible, sure: |
| 11 |
> |
| 12 |
> emerge -B package |
| 13 |
> mkdir /opt/package |
| 14 |
> tar -C /opt/package -xjf /usr/portage/packages/All/package-ver.tar.bz2 |
| 15 |
|
| 16 |
Yeah, but the internals'd be screwy; hardcoded paths would point to |
| 17 |
the /-based locations. Maybe (in effect) passing --prefix=/opt/$P to |
| 18 |
configure? |
| 19 |
|
| 20 |
> Smart, not really. Using portage to install packages that are outside of |
| 21 |
> portage's control is kinda silly. If you want to do that, build it by hand or |
| 22 |
> use a pre-compiled package such as a RPM or DEB from the author's site. |
| 23 |
|
| 24 |
But using portage lets you use emerge's dependency resolution, build |
| 25 |
system (ccache, distcc, etc), plus Gentoo patches and other fixes. With |
| 26 |
a rpm or deb you don't have the faintest clue what you're getting... |
| 27 |
|
| 28 |
Ed |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives