The reason I use the release sources is because presumably they are a
working set of files, free from any possible intermediate subversion
check-in bugs or code inconsistencies. I suppose if the releases
(0.99.6, ...) also carried with them an associated subversion revision,
then I could checkout the corresponding subversion revision instead of
using the posted release sources, but I am unaware of any such
association. For my own sanity then, I only use the posted release
sources so I have a known starting point from which to make my own
internal releases of Wireshark containing our company's proprietary
protocols.
So, if it's your recommendation to use the subversion sources rather
than posted sources, can the next 0.99.7 release also include the
associated subversion revision?
- Chris
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
> Sent: Friday, July 13, 2007 6:12 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] README.packaging is missing
>
>
> On Jul 13, 2007, at 12:57 PM, Maynard, Chris wrote:
>
> > In section 0.1 of the README.developer file, it says that you can
find
> > additional information "in the following README files", then lists
> > several of them. I noticed that README.packaging was listed, but
that
> > file does not appear to exist, or at least it's not being included
in
> > the 0.99.6 source distribution.
>
> It's not being included. I've checked in a fix to Makefile.am to
> include it and some other missing files.
>
> It's in the SVN tree (most developers should be using the SVN tree,
> either from SVN or from an SVN tarball, rather than the release
> tarballs).
-----------------------------------------
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.
