I'm packaging minisat2 for Fedora, and added some documentation

[David A. Wheeler]

Hi, I'm packaging miniSAT2 for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=453701

In the process, I created some documentation:
http://www.dwheeler.com/essays/minisat-user-guide.html

I'd be delighted to work with others who are packaging
SAT and other such tools for other distros (e.g., Debian).

--- David A. Wheeler

[Michael Tautschnig]

Hi David, hi all,

So I'm the maintainer of the Debian package and I'd be happy to share whatever
is there. It seems like some of my patches already made it into the Fedora
package, but documentation is actually a big weakness of my package, although it
at least offers (a not really complete) man-page. Debian requires that all
binaries are documented by man-pages -- is there no such need in Fedora?

David, your documentation seems to be very very nice. May I include it in the
Debian package as well?

Best,
Michael

[dwheeler]

> So I'm the maintainer of the Debian package and I'd be happy to share whatever
> is there.

It's a pleasure to meet you!

> It seems like some of my patches already made it into the Fedora
> package, but documentation is actually a big weakness of my package, although it
> at least offers (a not really complete) man-page. Debian requires that all
> binaries are documented by man-pages -- is there no such need in Fedora?

Fedora does not require man pages. Documentation is of course highly
preferred,
but the specific format is not required. I think I should create at
least
brief man pages when programs have nothing, so that Debian and Fedora
can
share as much as possible. I've already written a man page for Zenon,
a theorem prover that I've packaged for Fedora.

> David, your documentation seems to be very very nice. May I include it in the
> Debian package as well?

Absolutely, please do so!! I've released that document to the public
domain
(see the release at the bottom of the page), specifically
so that there'd be no issue in ANYONE including the documentation.
The current state is crazy; there's no way to use this tool without
at least a basic understanding of its input and output format.

I've already contributed my documentation upstream, in the hopes that
a future version
of this package will include at least some reasonable documentation.