On Tue, 25 Feb 2014, Brad Davis wrote:
On Tue, Feb 25, 2014 at 04:33:51PM +0100, Rainer Gerhards wrote:
Hi folks,
as you probably know, we get a new documentation thanks to the rsyslog-doc
project. I don't want to add all files individually to rsyslog. Would the
following work for you
a) two tarballs are being provided, one with source, one with doc
b) a single tarball is provided, but it contains the doc tarball as whole
c) anything else?
*I* would prefer a), but not sure if that's a decent choice for other
folks. Feedback appreciated.
As the current maintainer for rsyslog in The FreeBSD Ports collection, I
would prefer option B. To me it makes a lot of sense to ship
documentation with the product so people do not have to go far when they
have trouble.
For some reason, this seems very unpopular with some of the linux
distros.
I think a common ground that would make sense is a web build that updates
every day and shipping the latest build of docs with each release.
personally, I like having the docs as a separate package.
on servers or embedded devices, I don't need to waste the space on all the HTML
documentation that is really hard to use anyway.
it also makes point updates smaller on other systems, as they don't have to copy
over all the unchanged docs.
But it's not something I will be upset about either way.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
