On Dienstag 04 Mai 2010, Tomasz Rybak wrote:
> Hello,
> I have begun creating Debian PyCUDA (0.94 from GIT) package.
> It is my first Debian package and I was cheating
> by looking at other Python modules, but it seems to work,
> at least on my machine.
> In few days I should be able to check on another machine
> with Debian and CUDA, and will report if there are some problems.
> 
> Now I am wondering whether there is need to integrate Debian
> packaging metadata into PyCUDA (it is directory with few text
> files in it) and if so what is the best way to do it.

This is a great idea, ideally with the outcome that you would just
apt-get install python-pycuda and get a working setup.

Any DDs around? Anyone have spare cycles to make the packages?
There's also an ITP for PyCUDA:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546919
nvcc is apparently not packaged yet, either. Also the nvidia-glx
packages tend to lag by a version or so. (Currently they have 190.53.)

If we decide to go the home-rolled route:

I remember that a while back there seemed to be a debate by the debian
guys on whether a debian/ directory in upstream source is good or bad.
[1] Does anyone know what the resolution of that is by now? This would
determine whether I'd stick debian/ files into git.

[1] 
http://kitenet.net/~joey/blog/entry/on_debian_directories_in_upstream_tarballs/

Andreas

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PyCUDA mailing list
pyc...@host304.hostmonster.com
http://host304.hostmonster.com/mailman/listinfo/pycuda_tiker.net

Reply via email to