public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Lutgens <blutgens@sistina.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] make install suggestion/question
Date: Wed Jun 13 10:43:02 2001	[thread overview]
Message-ID: <20010613114157.A3813@minime.sistina.com> (raw)
In-Reply-To: <007901c0f421$45ef9080$c800000a@netlabs.local>; from lists@net-labs.de on Wed, Jun 13, 2001 at 05:55:30PM +0200

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

On Wed, Jun 13, 2001 at 05:55:30PM +0200, Holger Brueckner wrote:
>hi,
>
>here's my personal fix:
>
>mv /opt /usr/opt
>ln -s /usr/opt /opt

and how is this a) less places for binaries to be. and b) better. and c)
fhs2.1 compliant.

/usr/opt/gnome/bin is much more to type than /opt/gnome/bin. It's still
not dropping the binaries in /usr/bin.

I do not think that symlinks make you fhs2.1 compliant.

>
>:)
>Holger ... voted most angry looking #gentoo member ... *hehe*
>
>> Oops.  Well then, if that's the standard, all for it!  Maybe I shouldn't
>> write stuff like this so late at night ;).
>>
>> Thanks for setting me straight,
>> -Aaron
>>
>>
>> On 13 Jun 2001 02:25:32 +0200, Thilo Bangert wrote:
>> > hi aaron,
>> >
>> > Am Mittwoch, 13. Juni 2001 09:02 schrieben Sie:
>> > > I have question/suggestion.  Is it really necessary to put mozilla,
>> > > gnome and others in /opt?  I know it keeps it a bit more organzed and
>> > > such, but it really makes it a pain when compiling things. Some
>> > > programs, despite what they're told to use via the configure script
>> > > insist on using includes from /usr/include instead of
>> > > /opt/gnome/include.  If not changing it, at least provide sympolic
>> > > links or something (ie ln -s /usr/gnome/include/* /usr/include/ ).  I
>> > > think it would solve quite a few problems.
>> > >
>> >
>> > if i remember correctly does the Linux Standard Base define to put
>> > gnome, kde etc in /opt - so your "things" configure scripts/Makefiles
>> > should be adjusted to look there too/first.
>> >
>> > > -Aaron
>> >
>> > greetings
>> > Thilo
>> >
>> > _______________________________________________
>> > gentoo-dev mailing list
>> > gentoo-dev@cvs.gentoo.org
>> > http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>> >
>>
>>
>> _______________________________________________
>> gentoo-dev mailing list
>> gentoo-dev@cvs.gentoo.org
>> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>>
>
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@cvs.gentoo.org
>http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
Ben Lutgens		
Sistina Software Inc.	
Kernel panic: I have no root and I want to scream

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

  reply	other threads:[~2001-06-13 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 18:03 [gentoo-dev] make install suggestion/question Aaron Blew
2001-06-12 18:22 ` Thilo Bangert
2001-06-13  1:40   ` Aaron Blew
2001-06-13  1:41   ` Aaron Blew
2001-06-13  9:57     ` Holger Brueckner
2001-06-13 10:43       ` Ben Lutgens [this message]
2001-06-14  5:01       ` Achim Gottinger
2001-06-13  0:31 ` Mikael Hallendal
  -- strict thread matches above, loose matches on Subject: below --
2001-06-12 18:04 Aaron Blew

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=20010613114157.A3813@minime.sistina.com \
    --to=blutgens@sistina.com \
    --cc=gentoo-dev@cvs.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