Re: What is Wireshark 1.6.0 ?

[Gerald Combs <gerald () wireshark org>]

On 8/12/11 1:52 AM, news.gmane.com wrote:
> "Gerald Combs" <gerald () wireshark org> wrote in 
> message news:4E43F85A.6070809 () wireshark org...
> > If you take a fresh SVN checkout (*not* an export) of
> > http://anonsvn.wireshark.org/wireshark/releases/wireshark-1.6.0 and run
> > the following:
> >
> >  perl make-version.pl --package-version
> >  ./autogen.sh
> >  ./configure
> >  make
> >  make dist
> >
> > You should get your own copy of wireshark-1.6.0.tar.bz2 which is ready
> > to build on Windows, OS X, Linux, and UNIX. If your version of the GNU
> > build chain is close enough to the one running on the Buildbot builder
> > it will *probably* even be identical to the one available for download.
>
> But would this reproduce the "offically released source files" as mentioned 
> in section 3.3.4 of WSDG?

As I said, *probably*. I'm not going to guarantee that the Autotools
chain on your system will produce the exact same results as the chain on
the builder.

> Is the SVN release branch official or the wireshark-1.6.0.tar.bz2?

wireshark-1.6.0.tar.bz2 is official, in the sense that that's what is
published for download and listed (with md5, sha1, and rmd160 hashes) in
the release announcement. It is derived from the SVN release branch
using the steps listed above.


> Why should I use SVN checkout instead of export? The checkout generates a 
> lot of .svn directories that I only need when I modify the files and want to 
> check in probably later.

The .svn directories include a revision number which is used in a number
of places in the release packages. It's fetched with "make-version.pl
--package-version".


> I just want to find the best solution to get the header file and 
> supplementaty files that are necessary to compile my dissectors. Your 
> proposal to "make" the whole thing unfortuanately doesn't work because a 
> problem with the GeoIP library (see other thread).

I'm not proposing that you do anything. I'm trying to fill in gaps that
you seem to have already filled in with invalid assumptions.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe