What is lint-*.pl ? Is it a tool to automate a convertion of developers .spec to OpenPKG convention .spec ?
If there is a way to convert the developer .spec to a OpenPKG .spec without real understanding of all concepts and options of a .spec file I could try again to convert the .spec Thanks Alex Citando Michael Schloh von Bennewitz <[EMAIL PROTECTED]>: > On Wed, Aug 04, 2004, Alexander Belck wrote: > > Citando Michael Schloh von Bennewitz <[EMAIL PROTECTED]>: > >> Bill CAMPBELL graciously offered you the Courier IMAP package before, > >> and you'll even find a OpenPKG 2.1 version if you look around a little. > >> > > Yes, but at that time it allready was a bit outdated and I couldn't > > reuse/convert his .spec to a recent version of courier.src > > I searched under ftp://ftp.openpkg.org/release/2.1/SRC/[PLUS] and couldn't > > identify a package for courier. Is it renamed ? > > Is there an other place to search ? > > > There is no courier IMAP at all on the OpenPKG FTP server, so no that is not > what I meant. I was referring to Bill's server, although I don't know just > how public he wishes it to be. > > >> I believe that the reason before that we didn't integrate this version is > >> that it didn't meet all the OpenPKG package standards. I'll check to see > >> if this is still the case. > >> > > I don't remember issues about this, but I hope if there where problems that > they > > could be resolved yet. > > > After looking at his .spec file again, I see that the 2.1 courier IMAP > package heavily diverges from OpenPKG packaging standards. > > Although these standards are not yet well documented, the following > can give an eager packager an early start. > > 1 Install the openpkg-tools package > 2a Examine what you get (pay attention to lint-*.pl programs) > 2b [EMAIL PROTECTED] /opkg/bin/openpkg rpm -ql openpkg-tools > 3 Do something with it > > Just what to do with it? Maybe something like: > > [EMAIL PROTECTED] OPENPKG_PREFIX=/opkg OPENPKG_TOOLS_CMDPROG=/opkg/bin/openpkg \ > /opkg/bin/perl -I/opkg/lib/openpkg-tools/ \ > /opkg/libexec/openpkg-tools/cmd/lint-spec.pl \ > %_sourcedir/nmap/nmap.spec > > There is an easier way to do this, and it will be developed, tested, and > documented in the near future. We are developing a contributor environment. > > >>> I tryed to convert it to a openpkg-1.3.spec last year with no success due > my > >>> poor understanding of all the options in a .spec file. > >>> > >> If you really want it integrated into the OpenPKG package repository, > >> then consider beginning with Bill's package (which just might need very > >> few changes). > >> > > I realy couldn't do it before. His .spec was realy smaler than the one > provided > > by courier and I couldn't decide what could be taken out of the developers > > .spec ;-( > > > A typical OpenPKG .spec is one or two hundred lines long with the longest at > about four hundred lines. Just judging from the courier-imap.spec at almost > six hundred lines indicates to me that it's a hefty package, probably hard > to meet OpenPKG standards. > > -- > 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 > -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
