[JDEV] Jabber distribution test..

[Jeremie]

> Hmm. I like it, but I also would like to see it partially conform to the
> "standard" that seems to be existing in most packages. Notably, a tree
> looking like this :

Agreed... I was assuming what I knew about the "standard" based on the
hundreds, err, thousands of app installs I've done over the years across
various platforms :)

> /usr/local/jabber
> 
> 	README
> 	/bin (clients)
> 	/sbin (xrouter, transports, and scripts )

Ok, even better, I like the seperation, especially when both bin areas
start to grow. 

> 	/lib (libraries? currently they are all static, so this maybe unnecessary)
> 	/include (most likely unnecessary at this point as well)

Yeah, everything is static so that's not needed.  Maybe in the future with
the client lib or something similiar though.

> 	/man (yup)
> 	/share (not sure what the distinction is between this and the next one)
> 	/etc (but i do believe that the jabber.conf should be stored in one of them)

I definately like /etc instead.

> 	/logs (not necessarily conforming, but i like logs better than var)

Yes, /logs is happy... but we'll probably need a /var for the time being,
so that mod_basic can store/spool things on the filesystem(offline
messages, rosters, etc)

> I like the idea of putting all the files under one tree, rather than
> putting the man pages into a central directory. Most systems already have
> several different man paths, and although it may be trickier for a user to
> add the path, if they would want (heaven forbid) to delete jabber, it
> would be easy to do so.

Well, Jabber will be updated frequently, so it's probably best to keep it
as seperate as possible.  But I'm not sure about the man pages part... I
don't think it's a big deal to litter up /usr/local/man with this stuff,
it really doesn't take up space or effect functionality of anything, so I
don't see a problem with it... either way I guess it's no biggie since
it's configurable via ./configure :)

Jer