public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <dirk.heinrichs@online.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Installing outside of Portage & cruft removal
Date: Mon, 16 Feb 2009 22:09:12 +0100	[thread overview]
Message-ID: <200902162209.18251.dirk.heinrichs@online.de> (raw)
In-Reply-To: <gncjqo$79k$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Am Montag, 16. Februar 2009 21:54:51 schrieb Nikos Chantziaras:

> It's up the application to decide how to use prefix variable.  Most
> applications are respecting it.

Up to now, I didn't find one that doesn't. And if so, it'll receive a bug 
report right away.

> But you make it sound like it's
> impossible to not respect it, which is not true.

Well, if you don't, your package won't be spread widely until you've fixed it. 
You'll always find people who install sw as unprivileged user. If they can't 
install a package, they file a bug. Even some package managers build and 
install sw to a temporary directory as an unprivileged user to avoid messing 
up the system.

> I can write automake
> rules which completely ignore prefix.

Which in the end means the unprivileged user can't install your package. And 
even as root, I wouldn't. Nobody does this. It's a hipothetical case.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2009-02-16 21:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 16:41 [gentoo-user] Installing outside of Portage & cruft removal Grant
2009-01-26 16:48 ` Mike Kazantsev
2009-01-26 17:08   ` Jesús Guerrero
2009-01-30 18:45     ` b.n.
2009-01-26 17:35   ` Grant
2009-01-26 17:57     ` Mike Kazantsev
2009-01-26 23:17       ` Neil Bothwick
2009-01-26 17:57     ` Dale
2009-01-26 18:17       ` Grant
2009-01-26 18:26         ` Dale
2009-01-26 19:25         ` Paul Hartman
2009-01-26 20:21           ` Grant
2009-01-26 18:02     ` Rumen Yotov
2009-01-26 18:29     ` Daniel Pielmeier
2009-01-26 20:17       ` Grant
2009-01-26 20:24         ` Jesús Guerrero
2009-01-26 20:30           ` Grant
2009-01-26 20:44             ` Paul Hartman
2009-01-26 20:45               ` Paul Hartman
2009-01-26 20:51               ` Jesús Guerrero
2009-01-26 22:51                 ` Grant
2009-01-27 14:29                   ` Stroller
2009-01-27 15:29                     ` Hieu, Luu Danh
2009-01-27 22:34                       ` Grant
2009-01-27 22:57                         ` Paul Hartman
2009-01-26 20:44         ` Daniel Pielmeier
2009-01-26 22:31           ` Grant
2009-01-26 19:57     ` Jesús Guerrero
2009-02-15 20:49 ` Alex Schuster
2009-02-16 18:33   ` Grant
2009-02-16 18:41     ` Dirk Heinrichs
2009-02-16 20:31       ` Grant
2009-02-16 20:40         ` [gentoo-user] " Nikos Chantziaras
2009-02-16 20:48           ` Dirk Heinrichs
2009-02-16 20:54             ` Nikos Chantziaras
2009-02-16 21:09               ` Dirk Heinrichs [this message]
2009-02-17 18:22                 ` Grant
2009-02-17 18:35                   ` Dirk Heinrichs
2009-02-16 20:43         ` [gentoo-user] " Dirk Heinrichs

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=200902162209.18251.dirk.heinrichs@online.de \
    --to=dirk.heinrichs@online.de \
    --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