Hi,
Yes, it should be changed - in fact it should be removed.
It is not used in the build process or when running it from the U3 device.
It probably crept in when I was using an XML editor to develop the original
manifest.
The xsd itself comes from the U3 development kit but as far as I can tell,
there isn't a public reference for it, and other U3 apps don't reference a
schema in their manifests. Certainly the xsd shouldn't be under wireshark
version control.
I'll remove the reference when I've caught up.
Graeme
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Ulf Lamping
> Sent: 20 January 2007 18:06
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] U3 manifest refers to Ethereal
>
> Davide Schiera wrote:
> > Hi all,
> > the manifest for the U3 package is:
> > <u3manifest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >
> >
> xsi:noNamespaceSchemaLocation="C:\ethereal\packaging\u3\U3_man
ifest_1003.xsd
> > "
> > version="1.0">
> > ...
> > </u3manifest>
> >
> > where the noNamespaceSchemaLocation refers to a specific
> XSD file location
> > (c:\ethereal\.....). Shouldn't it be changed?
> >
> >
> Hi!
>
> I guess you mean the entry in the file:
> C:\wireshark\packaging\u3\win32\manifest.tmpl
>
> It might better read:
> C:\wireshark\packaging\u3\win32\U3_manifest_1003.xsd
> instead of:
> C:\ethereal\packaging\u3\U3_manifest_1003.xsd
>
> As that's where I expect this to be (the win32 path was also missing).
>
> However, this xsd file is not existing at the given place at all, and
> it's not even mentioned in the README.txt in that dir. where does it
> come from and for what is it needed?
>
> Regards, ULFL
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>