Bug#695311: marked as done (ITP: python3-csb -- Python framework for structural bioinformatics)
Your message dated Fri, 07 Dec 2012 11:54:48 +0100 with message-id 50c1caf8.1010...@tdido.com.ar and subject line Re: Bug#695311: ITP: python3-csb -- Python framework for structural bioinformatics has caused the Debian Bug report #695311, regarding ITP: python3-csb -- Python framework for structural bioinformatics to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 695311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wnpp Severity: wishlist Owner: Debian Med group debian-med@lists.debian.org * Package name: python3-csb Version : 1.1.0 Upstream Author : Michael Habeck michael.hab...@tuebingen.mpg.de * URL : http://csb.codeplex.com/ * License : MIT Programming Lang: Python Description : Python framework for structural bioinformatics Computational Structural Biology Toolbox (CSB) is a Python class library for reading, storing and analyzing biomolecular structures in a variety of formats, with rich support for statistical analyses. CSB is designed for reusability and extensibility and comes with a clean, well-documented API following good object-oriented engineering practice. ---End Message--- ---BeginMessage--- This ITP bug was opened by mistake, based on my misunderstanding of the concept of binary package in constrast to a full package when aiming for a python3 version of the project.---End Message---
Packaging InVesalius
Hi, After the packaging of python-casmoothing I started today the packaging of InVesalius 3. I've already packaged the last version to distribute to our users [1], but this package does not follow the Debian policies. As InVesalius source code [2] does not have a Makefile I created one and put it in the InVesalius source code and the package is read to done. Now I'm trying to do the packaging in the right way, following the Debian policies. I have the following question: How can I add a file (Makefile in my case) when doing the package? I was thinking in add the Makefile in the debian folder and put in debian/rules file a command to move the Makefile to the source code. Is this a good idea. Thanks! Thiago F. Moraes [1] - http://svn.softwarepublico.gov.br/trac/invesalius/wiki/downloads/3.0-beta-3#GNULinuxInstaller [2] - https://github.com/invesalius/invesalius3 -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cammolx_0iar50grh4xkv1rx_g+rqjncs3apd4xmk61wdvum...@mail.gmail.com
Re: Packaging InVesalius
Hi, On Fri, Dec 7, 2012 at 2:52 PM, Thiago Franco Moraes tfmor...@cti.gov.br wrote: I have the following question: How can I add a file (Makefile in my case) when doing the package? I was thinking in add the Makefile in the debian folder and put in debian/rules file a command to move the Makefile to the source code. Is this a good idea. d/rules is already a Makefile... why not copy/paste your existing Makefile into d/rules ? You may even make use of `dh_install` syntax instead of the lower level `install` command. 2cts -M -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CA+7wUsyE57NAVMEvaPe_m=2tf7pftha6gt5sw5uvtnpszsj...@mail.gmail.com
Re: Ten Simple Rules for the Open Development of Scientific Software
yeah -- they all forget about what they probably already rely upon. and imho article in 6 still needs an explicit Make a versioned release and possibly also -- support stable releases. On Fri, 07 Dec 2012, Andreas Tille wrote: Hi, feel free to read http://www.ploscompbiol.org/article/info:doi/10.1371/journal.pcbi.1002802 I just sended the authors the following remark via G+: I like your ten simple rules. What I'm missing in rule 7 and/or 8 is the idea that you should try to get your software included into distributions. In the field of Bioinformatics from a Debian/Ubuntu point of view Debian Med (http://www.debian.org/devel/debian-med) is your partner and also Fedora and SuSE have similar projects. Kind regards Andreas. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121207143916.gw7...@onerussian.com
Re: Packaging InVesalius
On Fri, Dec 7, 2012 at 12:01 PM, Mathieu Malaterre ma...@debian.org wrote: Hi, On Fri, Dec 7, 2012 at 2:52 PM, Thiago Franco Moraes tfmor...@cti.gov.br wrote: I have the following question: How can I add a file (Makefile in my case) when doing the package? I was thinking in add the Makefile in the debian folder and put in debian/rules file a command to move the Makefile to the source code. Is this a good idea. d/rules is already a Makefile... why not copy/paste your existing Makefile into d/rules ? You may even make use of `dh_install` syntax instead of the lower level `install` command. 2cts -M Hi Mathieu, It's a great idea. I'll take a look at 'dh_install' syntax. Thanks!. -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cammolx8gpxz-vcu4-wm3qx1e95hkgel4zfewcm5cwglg9rj...@mail.gmail.com
Re: Packaging InVesalius
Hi Thiago, On Fri, Dec 07, 2012 at 01:20:44PM -0200, Thiago Franco Moraes wrote: You may even make use of `dh_install` syntax instead of the lower level `install` command. It's a great idea. I'll take a look at 'dh_install' syntax. Additional hint which has proven to be given to newcomers: Please use dh_install via debian/*install files where you just name the files and the places where these should be moved to. That's the most simple and straightforward way to move files around - there are lots of examples using this (and BTW also python-casmoothing is using it ;-)). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121207154255.ga29...@an3as.eu
