Bug#811073: RFS: lbfgsb/3.0-1 [ITP]
On Wednesday 30 March 2016 14:27:45 Gianfranco Costamagna wrote:
> HI,
>
> >I didn't make one since upstream's tarball (at least for the latest
> >version) contains precompiled binaries, as well as a few files outside
> >of any directory (a little tarbomb). It is my understanding that these
> >need to be stripped out of the Debian source. Should I make a script
> >for that and have uscan run it?
> >
> >Upstream has a very slow release cycle, and it is my impression that
> >the library is more or less "done". Is a watch file still important?
>
> Filex-Excluded copyright keyword might become handy.
I see. I was under the impression that was only to be used when files
are excluded for copyright reasons. I repackaged the upstream tarball
because it included binaries (compiled from the source, one presumes)
and some metadata - not necessarily things that are problematic in a
copyright sense.
> please consider, other people might have to understand how did you
> do the work, and redo it.
That makes a lot of sense, yes.
> >There is no build system upstream. How should I best approach this
> >issue?
>
> add one :)
This'll be more work, so I'll have to postpone it a bit. The build
seems a bit trivial for a whole generic system to be added, doesn't
it?
> >- blas.f: We use the system libblas instead of this bundled copy.
>
> nice indeed
>
> >- driver*.f*: These are demonstration files for how to use the
> >
> > library, and are therefore not compiled. Should they be installed
> > as example source files somewhere?
>
> a package-examples might be trivial to add now, but you are the maintainer
> you have to know your users' expectations. If you think an example
> packages is useful you can add it.
I think they'll be useful, yes. I'll get around to adding that.
Reply to: