This is the mail archive of the
mailing list for the Cygwin project.
Re: [ITP] libungif-4.1.0-1
- From: Nicholas Wourms <nwourms at netscape dot net>
- To: Charles Wilson <cwilson at ece dot gatech dot edu>
- Cc: Lapo Luchini <lapo at lapo dot it>, CygWin-Apps <cygwin-apps at cygwin dot com>
- Date: Sat, 13 Jul 2002 08:34:36 -0400
- Subject: Re: [ITP] libungif-4.1.0-1
- References: <3D2F7992.email@example.com> <3D2FA5BF.firstname.lastname@example.org>
Charles Wilson wrote:
> Okay, while I think this package should be added to the
> really dislike the way it has been ported (sorry Lapo).
> Steven's 'mkdll.sh' script is just plain wrong. libungif
> libtoolized package, you should just relibtoolize.
> I've had I version of libungif around for a while -- it's
> I posted it some time ago when Harold thought he had more
time -- I
> thought you were basing your version on that, rather than
> Steven's mkdll.sh.
> BTW, you can also relibtoolize glib (and probably gtk) in
> way. Did I mention that I *really* dislike that mkdll.sh
I have to agree with Chuck, using a script is not the way to
go. You should try to get the package working within the
constructs provided. Using helper scripts can (and often
will) cause problems when (and if) the package releases a
new version. It is better to release a well tuned and fully
compatible package then to hastily release one based on (no
offense) kludges. If you run into any problems, post to the
main list and I'm sure one of us, who has seen it before,
will be able to help you fix it. As for the descriptions, I
usually just download the SRPM of the package I am building
from RedHat. I then use the short and long description from
the spec file as my basis. Plus, as an added bonus, you can
find nice patches for security and functionality that the
good folks at RedHat have provided.