Following up from what was discussed during the IRC meeting (see http://www.haz.cmsd.bc.ca/cgi-bin/kohalog.pl?date=29Aug02 for the full log) One of the items that was discussed was the creation of a Perl Bundle which would then be registered with CPAN (CPAN is the Comprehensive Perl Archive Network, see http://www.cpan.org). I agreed to look into the creation of such a bundle, which I managed to play with this afternoon and it is certainly feasable (and remarkably simple to do). This raises a couple of questions. (1) Who wants to register with CPAN (someone may already be so) and maintain the Bundle. Note: I am willing to take this role on. (2) The name of the bundle. Options that have already been mentioned are Bundle::Koha, Bundle::KohaSupport etc. (3) Because of the fact that the person who takes on the role mentioned in (1), must register with CPAN with the usual userid's and passwords etc, I think that another person should also have access to the userid and password so that we do not end up with a potentially unmaintained bundle (I propose either Pat or Katipo) (4) It was discussed about the installation of the yaz client as part of the Bundle. This we believe is possible but will need to be investigated further, at this point in time I propose that we use just the perl modules as they stand, and modify the documentation to include the fact that the yaz client must be installed prior to running the installer, or installing manually. (5) With the registration with CPAN, I believe that there is a potential delay of 1 to 3 weeks. I would suggest that we hold of on the next stable release for this period (unless the next release is only a day or two away). Thoughts and opinions appreciated - so are flames, but please flame me personally not the list ;-) Mike
Mike, thanks for taking on this role and getting started on it so quickly. I don't think that I often enough say how impressed I am with the care and effort that Koha volunteers put forth. (more comments below) On 30 Aug 2002, Mike Mylonas wrote:
Following up from what was discussed during the IRC meeting (see http://www.haz.cmsd.bc.ca/cgi-bin/kohalog.pl?date=29Aug02 for the full log)
One of the items that was discussed was the creation of a Perl Bundle which would then be registered with CPAN (CPAN is the Comprehensive Perl Archive Network, see http://www.cpan.org).
I agreed to look into the creation of such a bundle, which I managed to play with this afternoon and it is certainly feasable (and remarkably simple to do).
This raises a couple of questions.
(1) Who wants to register with CPAN (someone may already be so) and maintain the Bundle. Note: I am willing to take this role on.
Why don't you register bundle@koha.org, and we'll see about katipo creating an email address that forwards to you and to one or two other folks (to meet your point later about not having a single point of failure).
(2) The name of the bundle. Options that have already been mentioned are Bundle::Koha, Bundle::KohaSupport etc.
I like Bundle::KohaSupport ... my thought was that the bundle would be just of the modules we need to support us. If we decide to get more involved later, we can always add Bundle::KohaOpac and Bundle::KohaIntra for the app itself (thought I'm not sure this is the best way to go).
(3) Because of the fact that the person who takes on the role mentioned in (1), must register with CPAN with the usual userid's and passwords etc, I think that another person should also have access to the userid and password so that we do not end up with a potentially unmaintained bundle (I propose either Pat or Katipo)
(4) It was discussed about the installation of the yaz client as part of the Bundle. This we believe is possible but will need to be investigated further, at this point in time I propose that we use just the perl modules as they stand, and modify the documentation to include the fact that the yaz client must be installed prior to running the installer, or installing manually.
Sounds good for a first go 'round. I'd like to get the bundle out sooner rather than later, and something that does 80% now would still be a clear win.
(5) With the registration with CPAN, I believe that there is a potential delay of 1 to 3 weeks. I would suggest that we hold of on the next stable release for this period (unless the next release is only a day or two away).
Steve?
Thoughts and opinions appreciated - so are flames, but please flame me personally not the list ;-)
Mike
-pate
------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
On Fri, 30 Aug 2002, Pat Eyler wrote:
(5) With the registration with CPAN, I believe that there is a potential delay of 1 to 3 weeks. I would suggest that we hold of on the next stable release for this period (unless the next release is only a day or two away).
Steve?
Done. I probably need that much time to work out the kinks in 1.2.3 anyway. Steve.
Greetings all Progress has been made on obtaining the appropriate account accoutns etc for uploading modules into CPAN. We finally have a PAUSE ( Perl Authors Upload Server ) account, setup, and now we are just waiting on the registration of the namespace for the module, and confirmation for the namespace I believe will come through in the next day or two. On Sat, 2002-08-31 at 01:28, Pat Eyler wrote:
(2) The name of the bundle. Options that have already been mentioned are Bundle::Koha, Bundle::KohaSupport etc.
I like Bundle::KohaSupport ... my thought was that the bundle would be just of the modules we need to support us. If we decide to get more involved later, we can always add Bundle::KohaOpac and Bundle::KohaIntra for the app itself (thought I'm not sure this is the best way to go).
I have applied to get Bundle::Koha::Support with Bundle::KohaSupport as a 2nd option/choice, if anyone can see a problem with either please let me know asap. The final thing to make sure of is that we include all required modules in the bundle, which I have listed as..... DBI Date::Manip DBD::mysql HTML::Template Set::Scalar Digest::MD5 Net::Z3650 That leaves us with the only other requirement of the yaz client that would need to be installed. Can people please double check that I have included all required modules (I think they are right, but many eyes). In addition can people, let me know what modules will be required for any upcoming releases, I think that Steve mentioned at least one MARC module that will be required for the 1.3/1.4 releases. Look forward to your comments Mike
Tonnesen Steve wrote:
On 10 Sep 2002, Mike Mylonas wrote:
DBI Date::Manip DBD::mysql HTML::Template Set::Scalar Digest::MD5 Net::Z3650
Net::Z3950
and MARC::Record will be required for the 1.3/1.4 code.
G'morning all UNLESS steve has a good new, we can't use MARC::Record for instance : we had to modify it because the official release don't allow reading of a MARC record from a variable, but only from a file. The 4 lines added to enable reading from a variable were refused by MARC::Record maintainer, arguing we can save our variable to a file (but heavy perf loss !). Steve : something to add ? If it didn't change, we have to decide wether not to use the official MARC::Record, go to lobbying for our modif being included, or modify marcimport to use a file.
Good work, Mike!
I agree -- Paul
On Tue, 10 Sep 2002, paul POULAIN wrote:
Tonnesen Steve wrote:
and MARC::Record will be required for the 1.3/1.4 code.
G'morning all
UNLESS steve has a good new, we can't use MARC::Record for instance : we had to modify it because the official release don't allow reading of a MARC record from a variable, but only from a file. The 4 lines added to enable reading from a variable were refused by MARC::Record maintainer, arguing we can save our variable to a file (but heavy perf loss !). Steve : something to add ?
If it didn't change, we have to decide wether not to use the official MARC::Record, go to lobbying for our modif being included, or modify marcimport to use a file.
Steve and Paul, what is the status on this one? Is there something that I can do to help lobby the MARC::Record folks? -pate
-- Paul
Net::Z3950 will probably fail to install if the yaz client is not installed... perhaps we should leave this one out of the bundle for that reason for now? We could probably include the yaz client directly with Koha and offer to compile and install it when installing Koha... Would require that the machine has gcc and libc6 development libraries installed, and that the yaz license allows this. Steve.
On Mon, Sep 09, 2002 at 11:18:45AM -0700, Tonnesen Steve wrote:
Net::Z3950 will probably fail to install if the yaz client is not installed... perhaps we should leave this one out of the bundle for that reason for now? We could probably include the yaz client directly with Koha and offer to compile and install it when installing Koha... Would require that the machine has gcc and libc6 development libraries installed, and that the yaz license allows this.
Does yaz really require libc6? Just in the process of switching from libc5 to libc6, I'm still suspicious of anything that claims to "require" libc6; after all, glibc 2.x is not the only C library that is more comprehensive than Linux libc5. Just tried to compile yaz with my libc5 gcc, and got a bunch of errors; I guess I'll try to fix this up, since I still can't get perl to compile under my libc6 environment. -- Ambrose Li <a.c.li@ieee.org> http://trends.ca/~acli/ http://www.cccgt.org/ DRM is theft - We are the stakeholders
I have created a Bundle::KohaSupport to ease the installation of some of the supporting modules for Koha. At this point in time, the Bundle has been uploaded to the CPAN repository and has been accepted, now we are just waiting for it to make it onto the modlist so that people can install it using the 'perl -MCPAN -e 'install Bundle::KohaSupport' At this point in time until we can sort out some of the issues surrounding the Net::Z3950 and MARC::Record the bundle only installs the following modules Date::Manip DBI DBD::mysql Digest::MD5 Set::Scalar I would like to store the source that creates the bundle within the cvs repository so that all can contribute but we need to sort out where in the repository we store the code. One option that I discussed with Chris, was to create a new top level directory called cpan and then a sub directory under that for KohaSupport which leaves us the option of adding space for any additional modules that we might create. so the structure would look something like /cpan /cpan/KohaSupport /koha /koha/... /koha-html /koha-html/... Peoples thought ideas and comments please Mike
participants (5)
-
Ambrose Li -
Mike Mylonas -
Pat Eyler -
paul POULAIN -
Tonnesen Steve