[1466] in BarnOwl Developers
Re: Reorganizing perlwrap.pm
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Thu Oct 29 18:16:56 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@lunatique.mit.edu
Date: Sun, 24 May 2009 22:31:28 -0400
From: Nelson Elhage <nelhage@MIT.EDU>
To: Geoffrey Thomas <geofft@mit.edu>
Cc: barnowl-dev@mit.edu
In-Reply-To: <alpine.DEB.2.00.0905231333450.10796@lunatique.mit.edu>
On Sat, May 23, 2009 at 01:43:22PM -0400, Geoffrey Thomas wrote:
> Is this an appropriate time to think about moving to a less retarded
> naming scheme than e.g.
> barnowl/perl/modules/Jabber/lib/BarnOwl/Module/Jabber.pm, which manages
> to repeat every piece of information in its name once? What about just
> using perl/BarnOwl/Message/{Admin,Zephyr,Jabber,IRC,...}.pm?
>
> We can use makefile options to let you only copy subsets of perl/BarnOwl
> to the share directory, if we like the ability to have modules that
> aren't in the default build.
Hm. I do kinda like the way that the different modules are separated
out into their own hierarchies, but I see the argument. The
deeply-nested directories don't really bother me too much, on the
whole.
Does anyone else have a strong opinion?
> Don't forget to have an environment variable or command-line option to
> manually specify the location of the perl directory.
We support the BARNOWL_DATA_DIR env var, now that I'm no longer an
idiot and patched that code to work right.
Does anyone have thoughts on the cleanest way to detect that we're
running out of a build tree?
- Nelson
>
> --
> Geoffrey Thomas
> geofft@mit.edu
