Commit 216f66cb authored by felix s's avatar felix s

More verbose changelog.

Based on Carstens suggestions.
parent 7e3b41a2
gnucap (1:0.36~20171003-1) unstable; urgency=medium
* Split gnucap package into several packages
This is required, as gnucap now provides a shared library.
* libgnucap0 + libgnucap-dev (Closes: #224467)
enables custom executables or future packages using the library
These packages contain the shared library and provide the files neccesary
to build/link against it, respectively. For example users can create their
own binary programs to subtitute the "gnucap" example executable provided
in the "gnucap" package. Other packages may depend on libgnucap-dev, if
they make use ob the gnucap library.
* split off gnucap-default-plugins0 package
+ binary plugins
+ soname dependent pkglibdir
The plugins that were linked into the main executable previously are now
shipped as a separate (optional) binary, the "default plugins". These are
loaded by "gnucap", unless overridden in /etc/gnucap.rc (which is does not
exist by default). This package must hence be installed, if the
functionality of the previous gnucap package is sought.
The binary plugin is installed in a directory depending on the
architecture and on the library soname it has been tested against. Further
binary plugins should also be installed into this directory. The default
command for loading plugins uses the GNUCAP_PLUGPATH environment
variable to locate plugins, a colon separated list of paths.
* gnucap-common package (Closes: #693267)
this package provides the headers, required to load (some)
plugins at run time
* man pages for the three executables. these are no longer upstream.
* get-orig-source, snapshotting upstream git
there are no release tarballs, just tags, nowadays. these are
equivalent to releases ("development snapshots")
The headers are required, if plugins need to be compiled from within a
gnucap session, also for the purpose of libgnucap-dev, above. Further, these
headers are architecture independent. Hence this additional package.
None of the functionality supplied was present in previous packages.
* man pages for /usr/bin/gnucap and /usr/bin/gnucap-{conf,modelgen}. The
upstream project makes no attempt in providing these, hence they are
maintained here.
* get-orig-source target, snapshotting upstream git
There are no release tarballs, just tags, nowadays. these are equivalent
to releases ("development snapshots"). This is new and was not required for
previous tarball releases.
* set sysconfdir to /etc, equivalent to --sysconfdir in autotools.
this might become useful later.
(possibly override some things in /etc/gnucap.rc)
* update d/copyright
* move package to salsa (from alioth/pkg-electronics)
* debian/control: Bump Standards-Version to 4.1.3
Checked against
The seemingly relevant items do not require action.
- 5.6.26 VCS-*, "https", for example
- 10.2 plugins are in /usr/lib/triplet/gnucap0
- 4.15 reproducibility not formally tested
- 2.5 priority is optional
- 8.1.1 invokes ldconfig.
- 4.9.1 there is no doc (any more?) use wiki page instead
- 5.2 control does not mention -dbg packages
* bump compat to 11
* remove Wesley from Uploaders (Closes: #759987)
thanks for your work on this package!
* remove Hamish from Uploaders (Closes: #831480)
thanks for your work on this package!
* lintian override http in watch file
Now depend on dh >= 11. No action required, according to debhelper(7).
* remove Wesley J. Landaker and Hamish Moffatt from Uploaders as they not
active anymore
Thanking both for their work on the packages of gnucap in the past!
(Closes: #759987, #831480)
* adding a lintian override for http URL in watch file
Lintian is complaining about the usage of http:// instead of https:// on
the URL in watch, a file for automatic checking
for new upstream versions. isn't using the https protocol (yet or never will) and we need
to use http here. Note that tarball releases are currently suspended, and
git tags are used instead, so this might need more work.
[ Helmut Grohne ]
* Fix FTCBFS: Add gnucap:native to Build-Depends. (Closes: #878364)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment