Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Apr 2001 05:15:38 -0400 (EDT)
From:      "Albert D. Cahalan" <acahalan@cs.uml.edu>
To:        mwm@mired.org (Mike Meyer)
Cc:        acahalan@cs.uml.edu (Albert D. Cahalan), questions@freebsd.org
Subject:   Re: How Is The FeeBSD OS Like and Different Than Say Redhat or Suse LINUX
Message-ID:  <200104250915.f3P9FcB152869@saturn.cs.uml.edu>
In-Reply-To: <15077.30207.8849.168351@guru.mired.org> from "Mike Meyer" at Apr 24, 2001 07:47:59 AM

next in thread | previous in thread | raw e-mail | index | archive | help
Mike Meyer writes:
> Albert D. Cahalan <acahalan@cs.uml.edu> types:

>> Doesn't this make sense? If you compile a home-grown or self-ported
>> app for FreeBSD, where would you put it? I hope you don't dump it
>> in /usr/local with all the stuff provided by FreeBSD! It looks like
>> you need a /usr/local/local or /usr/local_I_REALLY_MEAN_IT for this.
> 
> Yes, but "ports are just pre-ported stuff to make your life simple" is
> the counterargument. Unless you want to treat the two differently, it
> really doesn't make any difference. Since I do want to treat them
> differently (because I can restore packages from the CDROM set), I
> agree with you, and set LOCALBASE= /usr/opt in /etc/make.conf.

That is a very reasonable place. SysV uses /opt and /usr/opt I guess.

>> Putting emacs under /usr/local is a relic from the days when
>> you'd buy a real UNIX system without emacs. It made sense,
>> since you were installing local (your site) additions. Now you
>> get emacs on a CD-ROM along with the rest of your OS.
>
> I've got emacs under /usr/local. That's because I didn't like any of
> the versions in the ports tree, so grabbed mine from xemacs.org. As
> such, it ain't on the CDROM set it goes in /usr/local, not /usr/opt.

Of course /usr/local is correct in this case.

> This does bring up a question - how many Linux package distribution
> systems let you change the installation point if you want to?

How many do not? Slackware maybe?

The package has to be created properly to be relocatable. The author
of the control file should use relative paths or paths with variables
in them, as appropriate for the packaging system. I seem to recall
that the RPM format even has a flag to indicate if this has been done.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104250915.f3P9FcB152869>