On Sat, Nov 16, 2002, Andrews, Martin wrote:

> To throw myself into openpkg (and because I want to play with rt) I thought
> I would try to get rt built. I saw it in the current tree and was excited
> because it appears to be a bear to get installed. Well - it appears to be a
> little tricky with openpkg too (okay, I know current is supposed to be
> unstable). The rt package (rt-2.0.15-20021005.src.rpm) does not list any
> build pre-reqs other than openpkg itself. I know there is a lot more - I
> started with perl-dbi and all its pre-reqs. Then I found that the rt.spec
> file had the wrong regular expressions for the rt Makefile - all the spaces
> should be tabs (I can provide a patch, but I suspect there is a better
> solutions than just replacing spaces with tabs - what kind of regular
> expressions does shtool support?). Anyhow - know I get a complaint that
> DBIx/DataSource.pm cannot be found (from DBIx::DataSource my perl research
> shows). I don't see perl module package that seems to fulfill that. Is there
> one? or is the rt package quite unready (the fact that as shipped it was
> using /usr/bin/perl I suspect it really does need some work)? Hope this does
> not come off as whining - I am really excited about openpkg instead of
> always rolling my own recipes for building open source software.

Outch, you performed the worst possible start with OpenPKG: with a JUNK
package in OpenPKG-CURRENT. Sorry, this by definition has to mean that
you have to fail 100% :-(

OpenPKG-CURRENT currently has the following packages (in decreasing
stability/completeness/etc order):

    class packages
    ===== ========
    CORE        22
    BASE       149
    PLUS       106
    EVAL       121
    JUNK        10

If you perform a "rpm -qpi rt*.src.rpm" you see that it is tagged (on
the Distribution: header) with [JUNK], so it belongs to the currently
ten packages in JUNK. And those packages are declared as such, because
they are fully broken. Under package-time, build-time and run-time!
Or in the case of "RT", the package was never finished at all.

So, if you're working with OpenPKG-CURRENT you only can count on CORE,
BASE and PLUS packages (because this means the package was already in
the previous release). EVAL might work, but you already should expect
problems. And JUNK you not even have to try. It by definition will not
even have a correct packaging.

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to