[1467] in BarnOwl Developers
Re: Reorganizing perlwrap.pm
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
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: Sat, 23 May 2009 13:43:22 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Nelson Elhage <nelhage@mit.edu>
cc: barnowl-dev@mit.edu
In-Reply-To: <20090522231830.GA18265@mit.edu>
On Fri, 22 May 2009, Nelson Elhage wrote:
> I'm getting annoyed at the huge perlwrap.pm file.
Me too...
> perl/lib/BarnOwl/*
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.
> instead just do a 'use BarnOwl' on startup.
This will make it possible to hack the perl parts without recompiling the
C, which would make me very happy.
> set its share directory to "$builddir/perl/", instead of the default
> compiled-in location. [...] The current motivation for perlwrap.pm is
> that by linking it into the binary, we ensure that a barnowl has enough
> perl statically linked in in order to be useful even without its share
> directory.
Don't forget to have an environment variable or command-line option to
manually specify the location of the perl directory.
--
Geoffrey Thomas
geofft@mit.edu
