Hi Gianfranco, Paul, thank you for assisting me.
I put the binary in a separated package.
Concerning the symbol file, it should be much better (after some study,
I realize, it wasn't clean at all :) )
I use now dh --with pkgkde_symbolshelper and this enables to use a oneliner such
as :
Hi,
>> BTW one single symbol file please>I recommend using the C++ support in
>> dpkg-gensymbols to achieve this,
>it is better than restricting particular symbols to particular arches
>etc.
this has to be read as:
"one single symbol file that covers every architectures please"
anyway,
On Fri, Apr 15, 2016 at 8:59 PM, Gianfranco Costamagna wrote:
> BTW one single symbol file please
I recommend using the C++ support in dpkg-gensymbols to achieve this,
it is better than restricting particular symbols to particular arches
etc.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Hi again
BTW one single symbol file please
no need to have an i386 with just two symbols differing from powerpc
https://sources.debian.net/src/libechonest/2.3.1-0.3/debian/libechonest2.3.symbols/you
can exclude them with (powerpc) or similar keywords
or something like this
Hi Frederic, still another question:
debian/rules.old <-- you might want to drop it
a libsphde1 library that has a binary...
usually libraries are installed by the dependencies, and the binaries are split
in separate packages.
please try to provide a package with the binary and the manpage,
Hi Jakub,
> *.manpages are mostly useful for manual pages that weren't installed by
> the upstream build system. (Perhaps the dh_installmanpages documentation
> should be more clear about it...)
>
> If the upstream build system did install them, you should use *.install
> files instead, where
* Jakub Wilk , 2016-04-07, 14:55:
*.manpages are mostly useful for manual pages that weren't installed by
the upstream build system. (Perhaps the dh_installmanpages
documentation should be more clear about it...)
Oops, I meant s/dh_installmanpages/dh_installman/.
--
Jakub
* Frederic Bonnard , 2016-04-07, 14:34:
debian/*.manpages, you can remove the "debian/tmp" prepending path I
think
surprisingly, I failed to do without.
*.manpages are mostly useful for manual pages that weren't installed by
the upstream build system. (Perhaps the
Hi Gianfranco,
thanks for your comments as usual,
> control: std-version is now 3.9.7
updated
> libjs-query can be left as-is, because using the internal debian jquery might
> result in a bad documentation
> package (look e.g.
> https://lists.debian.org/debian-devel/2014/10/msg00774.html;)
>
control: owner -1 !
control: tags -1 moreinfo
Hi,
control: std-version is now 3.9.7
libjs-query can be left as-is, because using the internal debian jquery might
result in a bad documentation
package (look e.g. https://lists.debian.org/debian-devel/2014/10/msg00774.html;)
this can simplify
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "sphde"
Package name: sphde
Version : 1.1.0-1
Upstream Author : SPHDE team
URL : https://github.com/sphde/sphde
License : EPL-1
Section : devel
11 matches
Mail list logo