Hi --

On Sat, 1 Oct 2005, Eivind Eklund wrote:

> The most important is being able to install binaries under $prefix/bin/,
> documentation under doc/<portname>/, examples under examples/<portname>,
> configuration under etc/, data under share/<portname> or similar,
> put databases under /var/<suitable location>, and put man/info pages
> under man/info respectively.  (Hopefully, nobody use info with a
> RubyGem, though.)  Prefix is /usr/local unless the user has set it differently.
>
> "Full" text below for convenience (I've cut down the hier manpage
> to be less noisy, only containing relevant directories):

[snip]

I respectfully suggest that the landscape of this discussion is
getting too cluttered.  Since arbitrarily many "repackaging"
philosophies and systems are possible, the specifics of this or that
particular system won't have a direct bearing on how a Gem can be
unpacked and reassembled.  I think it's more a matter of just having
Gems abstract their layout slightly (or make that possible), and then
having each repackaging person/team decide how they want to put the
Gem back together.

Or... maybe there could be an intermediate format, to which Gems could
be converted, that was sufficiently abstract to allow conversion to
other formats (a kind of hub-and-spoke approach).


David

-- 
David A. Black
dblack / wobblini.net