David O'Brien <[EMAIL PROTECTED]> types:
> On Sun, Dec 10, 2000 at 02:19:12PM -0600, Mike Meyer wrote:
> > > > I intend "LOCALBASE clean" to mean "all files installed by other ports
> > > > are looked for in the LOCALBASE tree".
> > > If all ports are PREFIX clean, you will have that. Thus it doe
On Sun, Dec 10, 2000 at 02:19:12PM -0600, Mike Meyer wrote:
> > > I intend "LOCALBASE clean" to mean "all files installed by other ports
> > > are looked for in the LOCALBASE tree".
> >
> > If all ports are PREFIX clean, you will have that. Thus it doens't need
> > to be discussed separately.
>
David O'Brien <[EMAIL PROTECTED]> types:
> > Wherease "PREFIX clean" means "all installed files are in the PREFIX
> > tree",
>
> Correct.
>
> > I intend "LOCALBASE clean" to mean "all files installed by other ports
> > are looked for in the LOCALBASE tree".
>
> If all ports are PREFIX clean, yo
On Sun, Dec 10, 2000 at 01:42:15PM -0600, Mike Meyer wrote:
> My bad - I coined the phrase "LOCALBASE clean" to describe a situation
> I've seen, without explaining the meaning.
You're mudding up things. You want to set LOCALBASE to /usr/foo and
ports should be "PREFIX" clean as that is what is
On Sun, Dec 10, 2000 at 02:18:51PM -0500, Brian Dean wrote:
> LOCALBASE just being the default value for PREFIX.
Not just. It is also where dependancies are looked for.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTE
Brian Dean <[EMAIL PROTECTED]> types:
> On Sun, Dec 10, 2000 at 01:02:09PM -0600, Mike Meyer wrote:
> > The problem is that *it doesn't work*. Well, not very well. Part of it
> > is that it's only given lip service: the porters handbook says "make
> > your ports PREFIX clean"; portlint doesn't do
On Sun, Dec 10, 2000 at 01:02:09PM -0600, Mike Meyer wrote:
> The problem is that *it doesn't work*. Well, not very well. Part of it
> is that it's only given lip service: the porters handbook says "make
> your ports PREFIX clean"; portlint doesn't do any checking about it.
> The porters handbook
Forrest Aldrich <[EMAIL PROTECTED]> types:
> Haha... okay, then what's the argument about.
> > You're about six years late. The ports system has used $PREFIX for
> > precisely this purpose since October 1994.
As Jacques pointed out, you set LOCALBASE in /etc/make.conf.
The problem is that *it do
In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
: Haha... okay, then what's the argument about.
People being too lazy to say PREFIX=/glortz in their /etc/make.conf
file.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Haha... okay, then what's the argument about.
> You're about six years late. The ports system has used $PREFIX for
> precisely this purpose since October 1994.
>
> DES
> --
> Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curr
Forrest Aldrich <[EMAIL PROTECTED]> writes:
> Within the scope of this problem, would it not be simple to code in a
> configuration diretive in the build process, such that a simple entry
> in /etc/make.conf would tell the ports build where to install ($prefix)?
You're about six years late. The p
On Sun, Dec 10, 2000 at 07:16:15PM +0100, Dag-Erling Smorgrav wrote:
> Forrest Aldrich <[EMAIL PROTECTED]> writes:
> > Within the scope of this problem, would it not be simple to code in a
> > configuration diretive in the build process, such that a simple entry
> > in /etc/make.conf would tell th
Within the scope of this problem, would it not be simple to code in a
configuration diretive in the build process, such that a simple entry
in /etc/make.conf would tell the ports build where to install ($prefix)?
Then, the local admin can make that decision.. whether or not to default
to /usr/loc
13 matches
Mail list logo
