Re: OpenSSL's MD5?

Stefan Walter <[email protected]> Tue, 3 Jan 2006 20:05:08 +0100
Newsgroups gmane.mail.spam.spamprobe.general
Organization Infinity Approximation Task Force
Message-ID <[email protected]>
Ossi Herrala, 03.01.06, 18:45h CET:

> On Tue, Jan 03, 2006 at 03:00:12PM +0100, Stefan Walter wrote:
> > Brian Burton, 03.01.06, 14:29h CET:
> > 
> > > release.  I plan to add support for jpg and png as well.  Do you think 
> > > these should be enabled/disabled separately?  Or maybe as a single 
> > > option such as --without-images or --disable-images?
> > 
> > Hm...I don't have a strong opinion on this. I don't know if there are
> > scenarios in which people would want to check only GIF attachments, but
> > not JPEGs or PNGs. A single option would probably be enough.
> > 
> 
> There might be a case where only libraries for GIF support are in the
> system. Or there might be GIF libraries and PNG libraries in different
> places. How should it work then?

What do you mean by "in the system" - "installed" or "available on the
platform"?

For package systems like FreeBSD's ports or NetBSD's pkgsrc, if you only
have libungif installed, the port/package should automatically install the
JPEG and PNG libraries via dependencies, so there's no problem. Or did you
mean (since you're a NetBSD guy;) that there might be platforms for which
one or more of these libraries might not be available? If you only have a
single switch in your port/package then, that'd mean you'd either get all
libraries or none of them. That'd be a reason to have separate switches,
yes.

As for libraries in different places: As long as they're all in the
include/library path, this shouldn't be a problem and the configure script
should find them all.

> Some softwares seems use configure options like this (some kind of defacto?):
> 
>  --with-jpg
>  --with-png=/path/to/png-library
>  --without-gif
> 
> For software packagers (like me for NetBSD's pkgsrc) it's convenient
> to have such wide range of options. This way it's easy to build binary
> packages with wanted depencies (and not to get ghost depencies from
> softwares autodetection features) and users building packages from
> sources can use the package framework to adjust the wanted depencies.

Agreed. However, I don't see any reason why someone would *want* to have
support for GIFs but not for JPEGs and PNGs.

(Note: I'm not against separate switches for all supported libraries at
all. I just want to understand your reasoning. If Brian adds a switch for
every supported library, I'm going to add independent options to the port
as well.)

Regards,
Stefan
signature.asc (application/pgp-signature, 650 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQGVAwUBQ7rK5FaRERsSueCzAQK5ygwAuQ3YCrrmmdM6KEHsEoUvv0ebrwG/1D1v
oBU9iYTf3XMYAWtL7ilLl7W5wreBd8KzaMeVIwL5lt1iPsBiRrLcaS0+ItbOWOuy
8R6TaeuQzCSBIQyDohfqcRUl5mduRXuaOPKnfbu9eRyu07QfAvnPdHyhtC+Px4zX
JQgp6+AonQDC0IVf20/lEJoOQg2JLGijn39WJiLJiY3qmKPrtZ+l1l66UFnnWJLO
9fAzGz3usifKoprn7uYBvtG68w9sjxGVu6M4wWl7pcTd9I/eW8SEkGUiydLD4kjG
bFSmup3zQKSDgE/HJil8uXbzgismK5KwGPMqCSfIXmb8dG4zkO9ENe5WbAgWf+Fr
LEKn/lcB/4jTVtXn9B7pd+snzamKOHpo3gaWh5P2t5qn+gCL1oSj7Ry5DfeHGvo7
m5KBs7druwFH9MN0Eh84XObrjp7bFFLtMbdrjKQHb+F2HhBOo8GVABUn5Wk60GG7
GTiUFWMZ+Jrglg3Oo9ay8vwQ82Y9kvXp
=UQuV
-----END PGP SIGNATURE-----