Actually the options are: -ta Build binary and source rpm from tarball -tb Build binary rpm only from tarball -ba Build binary and source rpm from given spec file (source must be where the spec wants it) -bb Build the binary rpm only from the given spec
When a working spec file is provided by the maintainer, building an rpm is very simple. Are the debian rules significantly different than those given in a spec file? Would it be feasible to make a packaging tool that would make a proper .deb if given the source and a spec file? I just think it would be a very good idea for all involved if a uniform description file was to be used for all (major) packaging systems. This would allow developers to maintain only 1 file and allow users/packagers to build any sort of package (debian or rpm) from the source. Just my $0.02. -D On Fri, Dec 22, 2000 at 06:15:40AM +0800, csj wrote: > I need to compile some stuff in Debian (available in Debian but three version > numbers stale). I have already successfully compiled them in Mandrake. > > The problem is that the application's various bits and pieces will be > splattered across my system. While they'll probably wind up in /usr/local, I > want a more manageable method of installing/deinstalling these files. I'm > thinking of creating a .deb to "trap" the compilation. > > Can someone give me a quick tip on how to do this, convert a tarball into a > deb in one fell swoop? I'm a bit lazy to RTFM. In Mandrake I simply type > something like rpm -bb (or is it rpm -tb?) to produce a binary from a > .src.rpm (I know, not quite a tarball). What's the quick and dirty Debian > equivalent?
