Ok, no separate glep for home installation:
So i need some clues how to install plugins into home - attached is some
ebuild patch sample (actually not a diff output) how i would try to start
with vim-plugins.eclass, as a discussion base.
Variables to be set by portage:
PREFIX=/home/haubi
On Tue, 24 May 2005 11:53:30 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| Variables to be set by portage:
| PREFIX=/home/haubi
| AFFIX=home/haubi/ (not used here)
Hrm. So what do we use for finding out where our non-home deps are
installed then?
| Where should additional documents
On Tue, May 24, 2005 at 11:07:54AM +0100, Ciaran McCreesh wrote:
On Tue, 24 May 2005 11:53:30 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| Variables to be set by portage:
| PREFIX=/home/haubi
| AFFIX=home/haubi/ (not used here)
Hrm. So what do we use for finding out where our
Jason Stubbs wrote:
On Friday 20 May 2005 21:30, Michael Haubenwallner wrote:
snip
But - aren't there many settings left over to the packages to decide,
at least to choose the package-defaults ?
Any package that does this is broken. There are a couple of cases where
there's no other
Jason Stubbs wrote:
snip
I intend that the package to be installed should not assume anything about
where its dependencies are and should query portage for them all.
Oh no, now many things get much clearer to me :(
But - aren't there many settings left over to the packages to decide,
at
On Friday 20 May 2005 21:30, Michael Haubenwallner wrote:
Jason Stubbs wrote:
snip
I intend that the package to be installed should not assume anything
about where its dependencies are and should query portage for them all.
Oh no, now many things get much clearer to me :(
But - aren't
On Thu, 19 May 2005 10:18:03 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| So unless it is shown otherwise, home install support requires:
|
| But imo the home-support _really_ requires another glep, as there
| are lots of more issuses than for the prefix-support.
Naah. Not really. The
Ciaran McCreesh wrote:
On Thu, 19 May 2005 10:18:03 +0200 Michael Haubenwallner
| But imo the home-support _really_ requires another glep, as there
| are lots of more issuses than for the prefix-support.
Naah. Not really. The hard part is figuring out how to correctly change
all shell
On Thu, 19 May 2005 13:05:20 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| Most of the packages (not ebuilds) wont work on systems without
| /bin/sh (Bourne-Shell, not bash) and /usr/bin/env, so there's no need
| to have a Bourne-Shell installed in /my/prefix/bin/sh instead of
| /bin/sh.
One general Question:
How can open source packages work on Unices which are non-Gentoo-Linux
if there are that many unresolved issues you try to point out ?
This is what autoconf and libtool are for, and if a package lacks using
them, autoconf/libtool-like trickery has to be done in ebuilds.
On Thu, 19 May 2005 14:46:34 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| How can open source packages work on Unices which are non-Gentoo-Linux
| if there are that many unresolved issues you try to point out ?
The issues I'm pointing out are things which are issues with the way
ebuilds
- Original Message -
From: Marius Mauch [EMAIL PROTECTED]
Ciaran McCreesh wrote:
snip
As for the new metadata variable, I think it should be a complement to
RESTRICT (not limited to prefix). As the name for this var I suggest
SUPPORTS, so for an ebuild that can install into /usr,
Michael Haubenwallner wrote:
- Original Message -
From: Marius Mauch [EMAIL PROTECTED]
Ciaran McCreesh wrote:
snip
As for the new metadata variable, I think it should be a complement to
RESTRICT (not limited to prefix). As the name for this var I suggest
SUPPORTS, so for an ebuild that can
On Mon, May 09, 2005 at 03:46:57AM +0300, Marius Mauch wrote:
Brian Harring wrote:
Clarify please :)
Offhand, I don't see why a bin repo for a home target isn't viable,
along with a vdb repo in the same location. It's a bit trickier, but
I suspect it might be a bit more flexible in the
On Sat, May 07, 2005 at 04:51:36PM +0100, Ciaran McCreesh wrote:
| If a dev doesn't have adequate knowledge for a particular package he
| shouldn't be fscking with it in the first place. So there said package
| can sit, having only the ability to install to / just like it always
| has until
On Sun, May 08, 2005 at 12:47:05AM +0900, Jason Stubbs wrote:
6 Portage must disallow the creation of binary packages where all
dependencies are not in the same PREFIX.
First level, second level... ?
I'd rather see the deps/prefix data slapped into the binpkg, and
tracked alongside, and
On Sun, 8 May 2005 02:58:32 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| Write the sucker up as a glep, issues and all for discussion, and you
| attack those involved as trying to bypass the discussion.
Bah. It should have been written up as a GLEP with the initial feedback
already
Brian Harring wrote:
Clarify please :)
Offhand, I don't see why a bin repo for a home target isn't viable,
along with a vdb repo in the same location. It's a bit trickier, but
I suspect it might be a bit more flexible in the long run.
I don't think that's possible without a lot of hacking for
On Sat, May 07, 2005 at 02:39:20AM +0100, Ciaran McCreesh wrote:
'tweak' is too mild a term... As far as I can tell I'm the only person
who's bothered to actually even try to look at this from an ebuild
perspective
Surprisingly, not quite true (was fun stating it I'm sure though).
-- not
Ciaran McCreesh wrote:
Ok, say we use ICANINSTALLTO (name!). Then if we have prefix as the
destination, there's no problem, because we know that all our deps are
installed in ${PREFIX} as well. However, if we're installing to home,
we need to know where our deps are -- for home installs I'm
On Sat, 7 May 2005 02:08:17 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| Re: changes, yes, things will need changes, and again, as stated
| thrice, those who want the changes are the ones who are stuck doing
| said changes. In other words, the actual work required to
| cleanse/correct the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 7, 2005, at 9:49 AM, Ciaran McCreesh wrote:
On Sat, 7 May 2005 02:08:17 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| Re: changes, yes, things will need changes, and again, as stated
| thrice, those who want the changes are the ones who are
On Saturday 07 May 2005 23:49, Ciaran McCreesh wrote:
Hrm. Being able to say I need xyz installed globally, and abc installed
either globally or at home level would work if and only if there was a
way of finding out where abc and xyz had been installed.
The being able to say is the harder
On Sat, 7 May 2005 10:31:49 -0500 Kito [EMAIL PROTECTED] wrote:
| Isn't going to work. A lot of these changes need package-specific
| knowledge that most people just don't have.
|
| If a dev doesn't have adequate knowledge for a particular package he
| shouldn't be fscking with it in the first
On Sun, 8 May 2005 00:47:05 +0900 Jason Stubbs [EMAIL PROTECTED]
wrote:
| I was planning to summarize home install support here, but your
| statement above has confused me a little. Is there any case where a
| package *must* have a dependency installed globally? If so, I can't
| see it.
I'm
On Fri, May 06, 2005 at 02:28:49PM +0100, Ciaran McCreesh wrote:
The problem isn't the packages. The problem is the ebuilds.
Agreed, although seemed to take a bit of dancing to get done to the
fact that yes, changing the prefix has a good chance of working.
From there, we're back to the old two
On Fri, 6 May 2005 20:05:18 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| On Fri, May 06, 2005 at 02:28:49PM +0100, Ciaran McCreesh wrote:
| The problem isn't the packages. The problem is the ebuilds.
| Agreed, although seemed to take a bit of dancing to get done to the
| fact that yes,
On Thu, May 05, 2005 at 03:48:49AM -0500, Brian Harring wrote:
default being use or use/local or whatever the hell
Wow.
no more posting at 3:50 am...
meant usr for above, pardon.
~brian
--
gentoo-dev@gentoo.org mailing list
On Thu, 5 May 2005 03:48:49 -0500 Brian Harring [EMAIL PROTECTED]
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
On Mon, 2 May 2005 21:48:10 -0500
Brian Harring [EMAIL PROTECTED] wrote:
Clarify why portage, which _does_ function as a secondary pkg manager
(collision-protect wouldn't exist otherwise) wouldn't suffice if
someone gave enough of a damn to do the work?
Off-topic, but collision-protect
Ciaran McCreesh wrote:
Oh, and by the way, we don't follow FHS.
This makes things easier, so what's better - to omit this completely,
or just say (without a reference to FHS):
This document prefers a filesystem hierarchy under this prefix as close
as possible to the current filesystem
On Monday 02 May 2005 21:22, Michael Haubenwallner wrote:
Hi ebuild devs,
Here's a glep draft now for (a part of) the long-term portage-goal
act as a secondary package manager ...
How about packages that usually install into /?
Regards,
Jason Stubbs
pgpbBCO46FIdq.pgp
Description: PGP
On Mon, 2 May 2005 19:02:29 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| State said problem for the general community. Guessing you're
| referencing the issue/request that being able to manage home, and
| 'global' installations?
|
| I'd still posit that the issue of installing to a user's
On Mon, 02 May 2005 14:22:15 +0200 Michael Haubenwallner
[EMAIL PROTECTED] wrote:
| Hi ebuild devs,
|
| Here's a glep draft now for (a part of) the long-term portage-goal
| act as a secondary package manager ...
Why did you post this without addressing the problems I pointed out to
you
Michael Haubenwallner wrote:
Hi ebuild devs,
Here's a glep draft now for (a part of) the long-term portage-goal
act as a secondary package manager ...
Comments welcome,
haubi
It's fancy, but what about ROOT? You don't like it just because you'd have
/usr/local/usr/bin/foo?
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Jackson wrote:
Michael Haubenwallner wrote:
Hi ebuild devs,
Here's a glep draft now for (a part of) the long-term portage-goal
act as a secondary package manager ...
Comments welcome,
haubi
It's fancy, but what about ROOT? You
On Mon, 2005-05-02 at 20:58 -0400, Alec Warner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Jackson wrote:
Michael Haubenwallner wrote:
Hi ebuild devs,
Here's a glep draft now for (a part of) the long-term portage-goal
act as a secondary package manager ...
On Mon, May 02, 2005 at 09:11:03PM -0500, Brian Jackson wrote:
Well, I've got a bug open to have a different variable like ROOT that
portage would read config files from. Maybe you could jump on that
bandwagon, and see if you can make things work that way.
Assuming you're referencing
38 matches
Mail list logo
