Re: Request for review: wip/py-EmPy

[Anthony Mallet <anthony.mallet%laas.fr@localhost>]

On Saturday, at 21:53, Thomas Klausner wrote:
| On Sat, Jul 14, 2012 at 02:12:59PM +0200, Anthony Mallet wrote:
| > - Did not define any CONFLICTS: the pkg installs a wrapper in bin, so the
| >   pkg may conflicts with itself if compiled for different python version?
| >   There are other such pkgs in pkgsrc (e.g. textproc/py-sphinx) but they do 
not
| >   add CONFLICTS either?
| 
| Look at py-anki, where I renamed the file in bin to have the python version 
as suffix.
| A number of packages do it this way to avoid the conflict.
|  Thomas

Yup, I already (manually) install a versioned bin/empy-${PYVERSUFFIX} script.

I added a bin/empy symlink in order to match what the debian (and others)
package provide, so that dependent sofware find what they may be looking
for. However, since none of the wrapper scripts are actually provided upstream,
I can also probably just remove the unversioned script, if that's pkgsrc
policy, and patch the dependent software configure scripts.

share/doc/empy is unversioned as well, so it would conflict with multiple
py*-empy installations. Should I add a version tag there too? IMHO that's a bit
odd, since empy documentation has nothing to do with python version.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
pkgsrc-wip-review mailing list
pkgsrc-wip-review%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-review