Re: Packaging software which does not use autotools

2006-08-21 Thread Michael Rasmussen
On 2006-08-21 13:53:01, Michael Rasmussen wrote: The deb-src are available here: http://mentors.debian.net/debian/pool/main/t/tptest3 You can find a more resent and polished version here: http://ftp.datanom.net/tptest3/ -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michae

Re: Packaging software which does not use autotools

2006-08-21 Thread Michael Rasmussen
On 2006-08-21 12:50:01, Guillem Jover wrote: I'm not talking about upstream but Debian ports (see below). Also you said you are taking over upstream, and reducing its portability seems as well a step back... It is not that I am removing something - except for stuff doing GUI for MS Windows a

Re: Packaging software which does not use autotools

2006-08-21 Thread Guillem Jover
As complement to what Wouter and Michael have replied... On Sun, 2006-08-20 at 23:24:49 +0200, Michael Rasmussen wrote: > What I have made is a generic package which just does not concerns > itself with other arches than for GNU/Linux. If people wants to compile > for *BSD or Solaris they can get

Re: Packaging software which does not use autotools

2006-08-21 Thread Wouter Verhelst
On Sun, Aug 20, 2006 at 11:24:49PM +0200, Michael Rasmussen wrote: > > On 2006-08-20 20:00:57, Guillem Jover wrote: > > > >If the current build system supports those arches, and yours does > >not, > You can hardly call it the "Current build system" as it is a number of > Makefiles in which you n

Re: Packaging software which does not use autotools

2006-08-20 Thread Michael Rasmussen
On 2006-08-21 00:40:09, Michael Banck wrote: libc6 is only available on GNU/Linux, you probably mean glibc. If that is the case, then it should probably be fine Correct:-) -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://keyserver.veridis.com:1137

Re: Packaging software which does not use autotools

2006-08-20 Thread Michael Banck
On Sun, Aug 20, 2006 at 11:24:49PM +0200, Michael Rasmussen wrote: > Which non-linux versions are you referring to? If the compile with > option -std=c99 and -pedantic showing no warnings or errors the ought > to be able to compile on any arch with gcc-4.1. Only dependency for > building it i

Re: Packaging software which does not use autotools

2006-08-20 Thread Michael Rasmussen
On 2006-08-20 20:00:57, Guillem Jover wrote: If the current build system supports those arches, and yours does not, You can hardly call it the "Current build system" as it is a number of Makefiles in which you need, manually, to add some defines. What I have made is a generic package which

Re: Packaging software which does not use autotools

2006-08-20 Thread Guillem Jover
On Mon, 2006-08-14 at 23:10:04 +0200, Michael Rasmussen wrote: > On 2006-08-14 22:33:49, Hendrik Sattler wrote: > > Do you plan to support other system than linux in a fork? If no, there > > is > Well, the software is already prepared to support *BSD, Solaris and > Linux, but I only intent to supp

Re: Packaging software which does not use autotools

2006-08-14 Thread Nathanael Nerode
Michael Rasmussen wrote: > Hi list, > > I have some questions I hope some of you have an answer for. > > I intend to package a peace of software which does not use autotools > but only has a plain Makefile. > > 1) Can I use dh_make? > 2) Does Debian policy have something to say about it? No. >

Re: Packaging software which does not use autotools

2006-08-14 Thread Wouter Verhelst
On Mon, Aug 14, 2006 at 09:50:51PM +0200, Michael Rasmussen wrote: > Hi list, > > I have some questions I hope some of you have an answer for. > > I intend to package a peace of software which does not use autotools > but only has a plain Makefile. > > 1) Can I use dh_make? Sure. > 2) Does D

Re: Packaging software which does not use autotools

2006-08-14 Thread Michael Rasmussen
On 2006-08-14 22:55:41, Sam Morris wrote: Sure, just customise the rules file it generates to not call a configure script. The rules file can really contain anything you want, as long as it builds a decent package when called. :) Nice, I have been accustomed to use dh_make and the various conf

Re: Packaging software which does not use autotools

2006-08-14 Thread Michael Rasmussen
On 2006-08-14 22:33:49, Hendrik Sattler wrote: Do you plan to support other system than linux in a fork? If no, there is Well, the software is already prepared to support *BSD, Solaris and Linux, but I only intent to support Linux - the only thing I use on a day to day basis. absolutely

Re: Packaging software which does not use autotools

2006-08-14 Thread Sam Morris
On Mon, 14 Aug 2006 21:50:51 +0200, Michael Rasmussen wrote: > I intend to package a peace of software which does not use autotools > but only has a plain Makefile. > > 1) Can I use dh_make? Sure, just customise the rules file it generates to not call a configure script. The rules file can real

Re: Packaging software which does not use autotools

2006-08-14 Thread Hendrik Sattler
Am Montag 14 August 2006 21:50 schrieb Michael Rasmussen: > I intend to package a peace of software which does not use autotools [...] > 3) Would it be ok if I converted it to use autotools my self? Do you plan to support other system than linux in a fork? If no, there is absolutely no gain in us

Re: Packaging software which does not use autotools

2006-08-14 Thread Carlos C Soto
Michael Rasmussen wrote: Hi list, I have some questions I hope some of you have an answer for. I intend to package a peace of software which does not use autotools but only has a plain Makefile. 1) Can I use dh_make? I don't think so, I hardly use debhelper but I think dh_make is used when

Re: Packaging software which does not use autotools

2006-08-14 Thread Michael Rasmussen
Hi again, Sorry, I forgot the must obvious question. 5) Would there be any interest in the community for be doing it? This question should have been numbered 1 since it is clearly a show-stopper:-) -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://