[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [MoM] Packaging fis-get


On Tue, Jan 24, 2012 at 07:05:22PM -0500, Dominique Belhachemi wrote:
> On Tue, Jan 24, 2012 at 6:48 PM, Luis Ibanez <luis.ibanez@kitware.com> wrote:
> > On Tue, Jan 24, 2012 at 5:55 PM, Andreas Tille <andreas@an3as.eu> wrote:
> >>
> >> On Tue, Jan 24, 2012 at 05:33:57PM -0500, Bhaskar, K.S wrote:
> >> >
> >> > >         debuild
> >> >
> >> > [KSB]  Considering that the two files above are the binary
> >> > distributions of GT.M as built by FIS, what should debuild do?
> >>
> >> Move these staigt inton the *.deb without changing anything.  This
> >> works here.
> >>
> >
> > Yes, I can confirm that with the second process
> > in my last email, the "pro..tar.gz" file is moved
> > by "debuild" into the debian directory.
> >
> I would expect to find the content of the generated tar.gz files in
> the debian/<packagename> directory, not the tar.gz file itself.

This is because Thorsten decided to move the complete tarball straight
into the *.deb package which is a very untypical decision and I was
reasoning about this several times in this thread.  So after a


it is correct to find a tarball in debian/<packagename> because this
is also in the *.deb.  If you do a

    make -f debian/rules clean

this should vanish and the debian/ dir should be as clean as before.

> It might help if you build a small package from the repositories and
> compare the output.

For these cases we have the hello package.  So an

  $ apt-get source hello
  $ cd hello-2.7
  $ debuild

might be a good exercise in any case but I think Luis is on the right

Kind regards



Reply to: