[wx-dev] RFD: Debian packages for wx 3.0
Stefan.Neis at t-online.de
Stefan.Neis at t-online.de
Fri Jun 13 09:13:37 PDT 2008
Hi,
> 1. Library packages:
> - libwxbase3.0 and libwxbase-{net,xml}3.0
> - libwxgtk-{adv,aui,core,gl,html,media,qa,richtext,src,xrc}3.0
Thinking of the poor person that might have to install things by
hand, I really dislike to have a dozen separate packages which
need to be installed in the right order to get to the point where
I might be able to start installing the application I originally was
interested in.
Having less packages IMHO clearly simplifies users' life here.
> 2. A single debug package libwx3.0-dbg containing symbols for all of
> the above.
BTW, does anybody have a reference to a nice description on how you
put the debugging symbols into a separate file and how you make use
of it? Or is it something that would be obvious once I upgraded to
gcc-4.x? (Sorry for the OT question...)
> 3. Development packages:
> - libwx3.0-headers containing all headers (excluding setup.h)
> - libwx3.0-dev containing wx-config, wxrc and setup.h
>
> 4. Documentation packages:
> - libwx3.0-doc containing HTML docs (I think one format is enough) -
> libwx3.0-examples containing all the samples and maybe demos (unless
> we prefer to include example in the doc package)
>
> 5. I18n package libwx3.0-i18n
2. to 5. sound good to me, but then I'm not a debian user anyway...
> Concerning the Debian files themselves I'd like to be able to specify
> the port we're building packages for ("gtk", "msw", "dfb", ...) when
> building them. I don't know if there is any standard about doing this
> but I hope it can be done -- any feedback from people more familiar
> with Debian packages would be welcome.
Maybe we would need to split stuff into a common package and into
port-specific pacakges? AFAIR, debian doesn't really like several
packages trying to install the same file(s)...
Regards,
Stefan
More information about the wx-dev
mailing list