headers
Markus Hoenicka | 19 Aug 2009 22:28
Picon

RefDB's source code organisation

Torsten Bronger writes:
 > Hallöchen!
 > 
 > I package RefDB for Ubuntu in order to make the server insallation
 > easier.  (Maybe eventually I'll upload it to the official Ubuntu
 > archives if nobody objects.)
 > 

This would be greatly appreciated by many users. I keep getting
requests about the outdated Debian repository that we used to have.

 > Apparatently, there used to be a Debianisation but I cannot find it.
 > Where is the old material for Debian/Ubuntu packaging (i.e. the
 > debian/ directory)?
 > 

I've checked the (usually disabled) CVS repository, but I couldn't
find a debian subdirectory. I faintly recall that the developer who
built the Debian packages did so in a local copy. Unfortunately the
debianization appears to be lost.

 > I'd like to have preferably only one package containing everything.
 > Unfortunately, RefDB is split into a couple of tarballs
 > (refdb-0.9.9.tar.gz, RefDB-perlmod-1.2.tar.gz,
 > RefDB-Client-1.18.tar.gz, RefDB-SRU-0.7.tar.gz, and
 > refdb-publist-1.1.tar.gz).  What should be packaged?  Since all
 > except the first package are tiny, what was the rationale to have
 > them separately?
 >
(Continue reading)

Permalink | Reply |
headers
Torsten Bronger | 21 Aug 2009 09:24
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Re: RefDB's source code organisation

Hallöchen!

Markus Hoenicka writes:

> Torsten Bronger writes:
>
> [...]
>
>> I'd like to have preferably only one package containing
>> everything.  Unfortunately, RefDB is split into a couple of
>> tarballs (refdb-0.9.9.tar.gz, RefDB-perlmod-1.2.tar.gz,
>> RefDB-Client-1.18.tar.gz, RefDB-SRU-0.7.tar.gz, and
>> refdb-publist-1.1.tar.gz).  What should be packaged?  Since all
>> except the first package are tiny, what was the rationale to have
>> them separately?
>
> The reason to keep them separately was to avoid unnecessary
> dependencies for packaging efforts. [...] Therefore the most
> "Debianish" way might be to provide separate packages for each
> tarball.

Good.  What are the dependencies *within* the above tarballs?  First
I though that all tarballs simply depend on refdb, so I packaged it
first.  Then, I found an SRU server in refdb-0.9.9.tar.gz, but the
Perl code for this is (probably) in RefDB-SRU-0.7.tar.gz.  So what
depends on what?

Tschö,
Torsten.
(Continue reading)

Permalink | Reply |
headers
Markus Hoenicka | 22 Aug 2009 00:09
Picon

Re: RefDB's source code organisation

Torsten Bronger writes:
 > Good.  What are the dependencies *within* the above tarballs?  First
 > I though that all tarballs simply depend on refdb, so I packaged it
 > first.  Then, I found an SRU server in refdb-0.9.9.tar.gz, but the
 > Perl code for this is (probably) in RefDB-SRU-0.7.tar.gz.  So what
 > depends on what?
 > 

That wasn't exactly easy to untangle. I've created a graph real quick
showing the dependencies:

http://refdb.sourceforge.net/refdb-dependencies.png

External applications or packages are shown in yellow. Perl modules
are shown in red.

Please correct me if there are any problems.

regards,
Markus

--

-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
(Continue reading)

Permalink | Reply |

Gmane