public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] /opt for binary only packages
@ 2006-09-08 12:13 Caleb Tennis
  0 siblings, 0 replies; only message in thread
From: Caleb Tennis @ 2006-09-08 12:13 UTC (permalink / raw
  To: gentoo-dev

I know that this is a convention we've followed (and is represented on the
ebuild howto guide), but is it set in stone?

The reason I ask is that I have a group of about 5 packages that I'm
working on ebuilds for that by default all want to be in
/opt/Pkgname-version.  I've done some ebuild foo to make it want to
install stuff in /usr/bin, /usr/lib, etc, but it also contains some extra
specification files that get used at runtime that it's expecting to easily
find, and leaving everything to just go into /opt/Blah is so much easier
to support.

So my question is: is it accept to install a package into /opt that isn't
strictly binary, but by default and design convention wants (and pretty
much needs) to be installed there?  I guess moreso I want to propose
changing the 'gentoo convention' for /opt to add in that it's okay to
install something in /opt that was designed to go there by its upstream
authors.

Thanks,
Caleb

-- 
gentoo-dev@gentoo.org mailing list



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-09-08 12:17 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-08 12:13 [gentoo-dev] /opt for binary only packages Caleb Tennis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox