public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A question regarding non-Portage software...
Date: Mon, 12 Mar 2007 20:52:21 +0200	[thread overview]
Message-ID: <200703122052.21217.alan@linuxholdings.co.za> (raw)
In-Reply-To: <200703111705.13436.wonko@wonkology.org>

On Sunday 11 March 2007, Alex Schuster wrote:

> Additionally, I like to have the stuff separated in sub-directories
> of /usr/local, and use stow or better xstow to create symlinks, so
> the software appears to be installed directly in /usr/local.

That sounds  like an awful lot of work, all for no additional 
benefit. /usr/local is for locally compiled pieces of software, and 
normally one runs 'make uninstall' in the code's src dir to remove it. 
Also, /usr/local is not supposed to have a hierarchy of sub-dir's (a'la 
windows) beneath it per LFS. /opt is a better choice for that.

As Bo and others have mentioned, an ebuild that you create yourself and 
place in a local overlay is by far the best solution, *especially* if 
the package installs just fine with './configure && make && make 
install'. In that case, the ebuild is literally just a few statements 
such as SRC_URI, HOMEPAGE and perhaps a DEPENDS if there are selectable 
configs. You gain all the benefits of stow plus all the benefits of 
portage, including emerge -C to remove the package from the system

Try it, it's WAY easier than most folk think it is

alan


-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2007-03-13 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-11  4:25 [gentoo-user] A question regarding non-Portage software Chris
2007-03-11  5:10 ` Bo Ørsted Andresen
2007-03-11  8:47   ` Neil Bothwick
2007-03-12  7:44     ` Nick Rout
2007-03-11  5:19 ` [gentoo-user] " »Q«
2007-03-12  9:47   ` Masood Ahmed
2007-03-11  5:21 ` [gentoo-user] " Michael [Plouj] Ploujnikov
2007-03-11 14:01   ` [gentoo-user] " Steve Long
2007-03-11 19:17     ` Bo Ørsted Andresen
2007-03-11 16:05   ` [gentoo-user] " Alex Schuster
2007-03-12 18:52     ` Alan McKinnon [this message]

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=200703122052.21217.alan@linuxholdings.co.za \
    --to=alan@linuxholdings.co.za \
    --cc=gentoo-user@lists.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