Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Francesco Pietra
Hi Andreas: I have seen your mail of Sunday, though I make my remarks here because they concern present debian package for i386. I am not going to details, only basic features from my personal viewpoint of potential user. Then, it is up to you to average the various requests. First, I must

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Andreas Tille
On Sun, 28 Jan 2007, Andreas wrote: 4. debian/compat The current debhelper version is 5.x. So if you have no certain reason (like backporting to Sarge for instance), I would recommend to use debhelper 5 here. I used the version 4 because otherwise I could not build the

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Charles Plessy
Le Sun, Jan 28, 2007 at 03:21:29AM -0500, Andreas a écrit : I have still one problem: Recognizing the PowerPC architecture. Currently the corresponding section in our configuration files looks like: PROCESSOR=`${UNAME} -m` if test `echo $PROCESSOR|${CUT} -c3` = ppc ; then

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Andreas Moll
Francesco Pietra schrieb: First, I must congratulate with you and your staff for this beautiful work. Then, I would like to see in the future a BAKMDL-type global conformational search in molecular mechanics. The basic step in any computational work with natural products, be that semiempirical

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Richard Laager
On Sun, 2007-01-28 at 09:45 +0100, Andreas Tille wrote: I'm replying to the reply, since I can't find a copy of the original message in my MUA. Sorry for the sub-optimal threading. On Sun, 28 Jan 2007, Andreas wrote: 4. debian/compat The current debhelper version is 5.x. So if

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Teemu Ikonen
On 1/28/07, Andreas [EMAIL PROTECTED] wrote: I have still one problem: Recognizing the PowerPC architecture. Currently the corresponding section in our configuration files looks like: PROCESSOR=`${UNAME} -m` if test `echo $PROCESSOR|${CUT} -c3` = ppc ; then ARCHITECTURE=ppc32

Re: BALLView - a molecular viewer and modeling tool

2007-01-28 Thread Andreas Moll
Teemu Ikonen schrieb: The code above causes a build failure in 32-bit powerpc, the uname -m output in this case is 'ppc'. The attached patch fixed this for me. Hi, thank you very much for the patch, it will be included in the next package version. I also built ballview on a 6-month old

Re: BALLView - a molecular viewer and modeling tool

2007-01-27 Thread Andreas
Hi, I have created a new version of package, that takes into account the following points: 2. The debian-upstream directory is a really interesting alternative to something we do not really like if upstream provides a debian directory. I have to

Re: BALLView - a molecular viewer and modeling tool

2007-01-26 Thread Andreas Moll
Hi, I have uploaded a new version of the package. As BALLview is a new package, if it fails to build on one architecture, its propagation to the testing distribution will not be impaired. This lets you one year or two to either fix the problem or drop arch support before inclusion in the next

Re: BALLView - a molecular viewer and modeling tool

2007-01-26 Thread Andreas Tille
On Fri, 26 Jan 2007, Andreas Moll wrote: I have uploaded a new version of the package. Well, I checked your work offline and my comments are concerning the version from tomorrow morning. So feel free to ignore issues that might be voided by your new version. I have changed the control file

Re: BALLView - a molecular viewer and modeling tool

2007-01-26 Thread Kevin B. McCarty
a very minor correction... On 1/26/07, Andreas Tille [EMAIL PROTECTED] wrote: On Fri, 26 Jan 2007, Andreas Moll wrote: I have uploaded a new version of the package. Well, I checked your work offline and my comments are concerning the version from tomorrow morning. So feel free to ignore

Re: BALLView - a molecular viewer and modeling tool

2007-01-26 Thread Andreas Tille
On Fri, 26 Jan 2007, Kevin B. McCarty wrote: I'm pretty sure you meant to say Architecture: any here. (For anyone who might need clarification: an Architecture: any package must Yes, Thanks for the hint. I hope this didn't come across as nitpicky, just wanted to make sure things were clear