[OPEN-ILS-DEV] Getting there -- bootstrapping OpenSRF Client problem

Mike Rylander mrylander at gmail.com
Sat Dec 16 17:18:59 EST 2006


On 12/16/06, Joshua Ferraro <jmf at liblime.com> wrote:
> On Sat, Dec 16, 2006 at 01:06:18PM -0500, Mike Rylander wrote:
> > On 12/16/06, Joshua Ferraro <jmf at liblime.com> wrote:
> > >Good point. So, shall I:
> > >
> > >1. remove MARC::* and JS::SM from the bundles?
> > >2. require specific versions in the bundle?
> > >        (which would throw warnings since they aren't on CPAN)
> >
> > (1) is more correct, since it's not the JS::SM version that is the
> > problem, but the libjs version (cvs version required -- c'mon,
> > Mozilla! Give us a new release already!) and attendant build switches
> > for both the C and Perl parts.  However (more below)...
>
> OK, I've updated the bundles as follows:
>

Did you read the rest of the message after "However" or the follow up
from Don?  If so, then I must not have explained myself properly.  The
discussion of a plan (which may or may not include the bundles) has
started.  There are other ways than bundles to keep CPANable
dependencies up to date, and in many ways they are superior.

I ask you to please stop issuing updates to these for the time being.
There's nothing anyone can do to stop you, of course, but until there
is more discussion surrounding the way forward for easing
installation, we will not be pointing to them from the wiki.  They are
causing installation/documentation churn in _two_ places now (wiki and
CPAN), and there are too many unknowns involved in blindly installing
the latest-and-greatest of everything from CPAN via a bundle.  In
addition, the cost/benefit ratio just doesn't make it worth the time
to doublecheck them every time we make a commit to CVS.  Yes, I mean
for both new and removed dependencies.

>
> OK with everyone if I update the docs to mention the bundles as an
> alternative way to install the perl mods once other prereqs have been
> met?
>

No, that's not ok.  They are not tested for use in installing
Evergreen, and they represent a "package" attached to the project and
would be expected to "just work" because it has a version number
stamped on it, where as the wiki is a living document (with
disclaimers of incompleteness where appropriate) that is expected to
change and evolve over time.

I'm working on a full proposal for a packaging and deployment system
(in abstract for now) that we can all work on over time but should
provide some immediate benefit long before the entire thing is
complete, so (all) please stay tuned for that.  I'll try to finish it
up tonight or tomorrow morning (holiday guests are over right now, but
I'll find some time ;) ).

-- 
Mike Rylander
mrylander at gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org


More information about the Open-ils-dev mailing list