Graham,
Hmm, if you browse to the releases folder from the link you sent, it
does seem that there is a subversion revision associated with each
release after all. For example, wireshark-0.99.5 appears to be
synonymous with subversion revision 21263. So once 0.99.6 is available
in the same releases folder, it too should have an associated subversion
revision and I (and other developers) could use that revision as our
starting points instead of using the posted sources from
http://www.wireshark.org/download/src/wireshark-0.99.6.tar.gz.
- Chris
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> bounces@xxxxxxxxxxxxx] On Behalf Of Graham Bloice
> Sent: Monday, July 16, 2007 4:15 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] README.packaging is missing
>
> Maynard, Chris wrote:
> > 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?
> >
>
> I would suggest that you use the "releases" branches in svn. See
> http://anonsvn.wireshark.org/viewvc/viewvc.py/releases/, although it
> appears
> that 0.99.6 has it's own little special place at the moment. Gerald?
>
> --
> Regards,
>
> Graham Bloice
-----------------------------------------
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.