A few questions..
1: What is a good way for handling the version fields to reflect that
the upstream version is a beta? In this case the upstream version is
1.05beta10, leaving me with a bit of a problem (for when 1.05 is
actually released)..
Note that I do have a good reason for packaging the beta version and not
the stable release before it..
2: Would anyone be willing to look over my package and make sure that it
does not violate policy? Currently the only lintian warning is a
ancient-standards-version, which I am not wanting to bump up to current
until I'm sure its compliant..
3: I've got a package which can be compiled with or without X support,
However the X support does not work without changing a few settings in
the X config, as I don't use X I'm not the best one to try and figure
out what to do..
4: This package can also be compiled for 2.0 kernel or for 2.1 kernels,
but not both, what's the best way to handle this?
Thanks..
Zephaniah E, Hull..
Mercury on IRC.
--
PGP EA5198D1-Zephaniah E, Hull <warp@whitestar.soark.net>-GPG E65A7801
Keys available at http://whitestar.soark.net/~warp/public_keys.
CCs of replies from mailing lists are encouraged.
Attachment:
pgpl0PTJUPg4_.pgp
Description: PGP signature