-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Feb 03, 2003 at 03:38:11PM -0600, Kenneth Pronovici wrote:
> I've now noticed that this doesn't conform to policy and I'm a little
> confused about what packages I should provide.
Only the name of the module package is against policy - it should be
python-pythoncard.
> Should I provide the package python-pythoncard that depends on on python
> (>=2.2), python (<<2.3), or should I instead provide python2.2-pythoncard
> that depends on python2.2 and also python2.3-pythoncard that depends on
> python2.3?
See below.
> This is getting a bit more complicated than I expected it to be. I'd
> appreciate any advice you can give me.
I don't know why you split docs and samples, I'd put them in one package,
the samples go into /usr/share/doc/<package>/examples/. The doc package
depending on either of the library packages. The user can decide
which pythoncard version to use for the samples.
python2.2-pythoncard Depends: python2.2
python2.3-pythoncard Depends: python2.3
pythoncard-doc Depends: python2.2-pythoncard | python2.3-pythoncard
Greetings,
- --
Bastian Kleineidam
Atombombe · Plutonium · Fat Man · Do it Yourself · Tim Taylor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+P6gJeBwlBDLsbz4RAiuIAJ9JnatTa0a8+KFCbbG7W6bMAA8cNwCfUtxy
80MB+Mw9N6GDtsjxd0sGn6k=
=hNRy
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
