Re: Custom zlib for Windows builds

[Pascal Quantin <pascal.quantin () gmail com>]

2015-04-27 20:43 GMT+02:00 Gerald Combs <gerald () wireshark org>:

> On 4/27/15 8:57 AM, Pascal Quantin wrote:
> > 2015-04-27 17:55 GMT+02:00 Graham Bloice <graham.bloice () trihedral com
> > <mailto:graham.bloice () trihedral com>>:
>
> >     I'll have a go at producing a new one, what name do we give it
> >     zlib-1.2.8-ws?
> >
> >
> > That's our usual naming scheme yes.
>
> Would a "wireshark-windows-thirdparty" repository be useful for managing
> this? I've been thinking about adding something for the scripts I use to
> create the OpenSUSE-derived packages.

What would we use it for? Storing the scripts / patches used to generate
the packages? If yes, I guess storing those in the zip file (as you started
to do for some packages) makes it easier to find the relevant info
(typically I should have added the steps - including the compilation flags
- used to generate libgcrypt, instead of saying that it was compiled
without AES-NI support).
Or we could eventually create a folder per package in this new repository,
and then put the relevant stuff (and replace it each time we upgrade the
package). But I fear it would make it harder to find the info afterwards.
Or maybe you had something else in mind?

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe