public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new glep draft: Portage as a secondary package manager
Date: Thu, 5 May 2005 15:01:05 +0100	[thread overview]
Message-ID: <20050505150105.7fc5f5de@snowdrop> (raw)
In-Reply-To: <20050505084849.GC13705@exodus.wit.org>

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

On Thu, 5 May 2005 03:48:49 -0500 Brian Harring <ferringb@gentoo.org>
wrote:
| > Ok, here's the main issue. Simply changing prefix isn't enough to
| > automatically make every package in the tree work. A heck of a lot
| > of them will need manual modification, and there's no easy way to
| > figure out which these are. So...
| 
| Err.  ROOT!="/" exists already, and directly screws with prefixes.  So
| this doesn't seem particularly valid in light of that fact.

No, root doesn't screw with prefixes.

| > Thing is, if we introduce the PREFIX feature, people will expect it
| > to actually work. It won't, at least not straight away, because
| > there are so many ebuilds that use more than econf to get the prefix
| > figured out. By whitelisting we can at least display a nice "you
| > can't install this package in a prefix" message.
| 
| Not a valid arguement to exempt even trying.
| 
| Consider if people used that arg for avoiding porting linux to new 
| arches-  Linux would still be strictly x86.

Eh? No, see, we have KEYWORDS, which indicate whether you can use a
package on a given arch.

| > Yet another issue... As it stands, all deps must be installed into
| > the given PREFIX. This is messy. Is there a way around this?  This
| > would be less of a problem with ICANINSTALLTO="home" -- presumably
| > for these portage could pass a var to the ebuild telling it in which
| > prefix to look for its deps.
| 
| injections, mainly.

Nasty hack.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-05-05 14:01 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 12:22 [gentoo-dev] new glep draft: Portage as a secondary package manager Michael Haubenwallner
2005-05-02 14:13 ` Ciaran McCreesh
2005-05-03  0:02   ` Brian Harring
2005-05-03 12:53     ` Michael Haubenwallner
2005-05-03 14:12     ` Ciaran McCreesh
2005-05-05  8:48       ` Brian Harring
2005-05-05  8:55         ` Brian Harring
2005-05-05 14:01         ` Ciaran McCreesh [this message]
2005-05-06  5:09           ` Brian Harring
2005-05-06 13:12             ` Brian Jackson
2005-05-07  1:07               ` Brian Harring
2005-05-06 13:28             ` Ciaran McCreesh
2005-05-07  1:05               ` Brian Harring
2005-05-07  1:39                 ` Ciaran McCreesh
2005-05-07  7:08                   ` Brian Harring
2005-05-07 14:49                     ` Ciaran McCreesh
2005-05-07 15:31                       ` Kito
2005-05-07 15:51                         ` Ciaran McCreesh
2005-05-08  7:58                           ` [gentoo-dev] new glep draft: Portage as a secondary package manager OT Brian Harring
2005-05-08 15:22                             ` Ciaran McCreesh
2005-05-07 15:47                       ` [gentoo-dev] new glep draft: Portage as a secondary package manager Jason Stubbs
2005-05-07 20:02                         ` Ciaran McCreesh
2005-05-08  8:33                         ` Brian Harring
2005-05-09  0:46                           ` [gentoo-dev] new glep draft: Portage as a secondary package manager, [gentoo-dev] Marius Mauch
2005-05-09 10:54                             ` [gentoo-dev] new glep draft: Portage as a secondary package manager Brian Harring
2005-05-19  8:18                         ` Michael Haubenwallner
2005-05-19  8:30                           ` Ciaran McCreesh
2005-05-19 11:05                             ` Michael Haubenwallner
2005-05-19 11:19                               ` Ciaran McCreesh
2005-05-19 12:46                                 ` Michael Haubenwallner
2005-05-19 19:42                                   ` Ciaran McCreesh
2005-05-19 13:01                           ` Jason Stubbs
2005-05-20 12:30                             ` Michael Haubenwallner
2005-05-21  1:22                               ` Jason Stubbs
2005-05-23  7:11                                 ` Michael Haubenwallner
2005-05-07  9:58                   ` Marius Mauch
2005-05-12  7:56                     ` Michael Haubenwallner
2005-05-12 23:44                       ` Marius Mauch
2005-05-03 12:54   ` Michael Haubenwallner
2005-05-02 19:15 ` Brian Jackson
2005-05-03  0:58   ` Alec Warner
2005-05-03  2:11     ` Brian Jackson
2005-05-03  2:48       ` Brian Harring
2005-05-03  3:16         ` Brian Jackson
2005-05-03  6:05         ` Marius Mauch
2005-05-03 12:54         ` Michael Haubenwallner
2005-05-03 12:54     ` Michael Haubenwallner
2005-05-03 13:22 ` Jason Stubbs
2005-05-07 11:18   ` Michael Haubenwallner
2005-05-24  9:53 ` Michael Haubenwallner
2005-05-24 10:07   ` Ciaran McCreesh
2005-05-24 10:43     ` Brian Harring
2005-05-24 12:21     ` Michael Haubenwallner

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=20050505150105.7fc5f5de@snowdrop \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@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