On Sat, Feb 19, 2005, OpenPKG Project Robot wrote:
> The following OpenPKG Contribution Area operation occurred.  uploaded RPM
> file "ripe-whois-tools-2.4-20050218.src.rpm" accepted -- moved to contrib
> area.  No action is required on your part.
>
Thanks for the contribution.

> Information about ripe-whois-tools-2.4-20050218.src.rpm follows:
> | Name:     ripe-whois-tools          Source RPM:   (none)
> | Version:  2.4                       Signature:    
> md5:db503b7fa5a1cd714aaf3494c532a909
> | Release:  20050218                  Build Host:   fozzie.ziew.org
> | Group:    Network                   Build System: sparc64-solaris10
> | Class:    EVAL                      Build Time:   Sat Feb 19 16:19:22 2005
> | Distrib:  OpenPKG                   Install Time: (not installed)
> | License:  RIPE NCC                  Install Size: 12217 bytes
> | Packager: The OpenPKG Project       Relocations:  (not relocateable)
> | Vendor:   RIPE NCC
> | Summary:  RIPE Whois Tool
> | URL:      http://www.ripe.net/ripencc/pub-services/db/
> | Description:
> |     The RIPE version of the whois client program.
> |     This is intended for European users as it will query a RIPE whois
> |     server with extended whois capabilities rather than a standard whois
> |     protocol server. The whois program is fully compatible with the
> |     standard whois protocol and can thus replace your default whois
> |     program.
> | Files:
> ______________________________________________________________________
> The OpenPKG Project                                    www.openpkg.org
> Developer Communication List                   openpkg-dev@openpkg.org
>
I'm not quite sure why this contribution ocurred, but here's some
information for the nice person who offered it.

A package already exists with the RIPE whois client, called ripe-whois in
the PLUS class. The already existing package includes a newer (version 3.X)
whois client that can do IPv6 and some other modern features not found in
the older version 2.4. Also check out the 'with_altport yes' option in the
existing package, which causes the client by default to use the same port as
the RIPE server (server package is called ripe-dbase).

There is an even newer version of the RIPE whois client that is not packaged
due to being part of the server software, which we can further discuss if
needed.

Regards,
Michael

-- 
Michael Schloh von Bennewitz <[EMAIL PROTECTED]>
Development Team, Operations Northern Europe
Cable & Wireless Telecommunications Services
Tel +49-89-92699-227, Fax +49-89-92699-808

Attachment: pgp11s2HMPFrs.pgp
Description: PGP signature

Reply via email to