similar to: Some automake help?

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a lot Stuart and others. Kudos for the work! NUT revamp is not yet

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%d` \

With the AsciiDoc conversion underway, I am wondering if we should keep the AsciiDoc for the driver man pages in a specially-formatted comment in the driver (taking a cue from the comments specifying USB information). I have been doing something similar with the tripplite_usb driver for a while - it contains Perl-style POD (Plain Old Documentation) in a C comment, and the man page can be

3a. What part of the documentation needs the most immediate attention? 3b. Will anyone come after me with an axe if I move the entire corpus to ASCIIDOC markup? http://www.methods.co.nz/asciidoc/ 3c. Why isn't the content of the website a branch in the repo? Can we fix things so it is? Hint: If the website becomes a repo branch, I'll reorganize and rewrite that for clarity, too. --

I was trying to merge the Debian unstable packaging files with the NUT trunk, and I noticed a bit of a problem with the automake changes. For the uninitiated, the 'debian/rules' file is essentially a Makefile that is used to build the package and split things into the sub-packages. If you look at line 85 of this copy of the rules file:

[the mailing list you want is nut-upsuser.] On Mon, Aug 3, 2009 at 8:05 AM, Blagovest Kolenichev wrote: > Hi, all > > I had fail to find in the supported hardware page > > http://www.networkupstools.org/compat/stable.html > > support for "NOVA AVR 625", but see that "NOVA AVR 600 Serial" > is supported. Can you tell us is there a big difference between

Hello list, I have explored https://github.com/networkupstools/nut repository and found that Riello UPS added into list of supported UPS. But current package for most distribution it's nut-2.6.5 which doesn't have Riello's models. Do we need to wait next upcoming nut release to get start with Riello? I tried to install from source but stuck: # git clone

In r2124 of branches/AsciiDoc (haven't checked where else this is), it looks like we have two duplicated columns. See diff below. This results in the model name showing up in the driver column of the HCL. How is driver.list regenerated from driver.list.in? Do I just need to re-run autoreconf to get the rules up-to-date? Or is this converted manually for the time being? diff --git

> The Buildbot has detected a new failure of Ubuntu-lucid-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-lucid-x86/builds/78 If I understand this correctly, there are multiple copies of some of the man page names in the automake variables: /usr/bin/install -c -m 644 ../../../docs/man/nut.conf.5

All, With AsciiDoc, we can make use of some macros to cut down on some of the repetition in the driver man pages. I don't want to go overboard on this, though - I know that drivers aren't meant to be invoked directly by users anyway. I propose that we put all of the gory details into the nutupsdrv(8) man page (mostly there anyway), and just add a few basic options to the

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Fri Dec 17 23:32:20 2010 > New Revision: 2748 > URL: http://trac.networkupstools.org/projects/nut/changeset/2748 > > Log: > --with-doc=auto now behave depending on AsciiDoc presence Instead of building whatever can be build (depending on the versions found), you now have changed the

Arnaud, my UPS arrived yesterday; thanks for your generosity. I'm using it to power the computer I'm typing on. This moves NUT up a few places on my priority list. In our last email exchange, I believe we agreed on a couple of major points. I want to confirm these before I start modifying the documentation heavily. 1. asciidoc is a good master format for the in-tree documentation. 2.

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

I would like to learn AsciiDoc. Is there any good examples how to use AsciiDoc with R? I know that there is packages called ascii to do this, but it would be nice to see some examples how AsciiDoc works with R. Is there an AsciiDoc distribution for Max OS X? -Johannes

On Oct 21, 2014, at 11:37 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hummm, that got me past that barricade, but then it needed asciidoc, which > pulled in everything else it was fussing about. The everything else was > close to all of tex and latex, something north of 220 megs worth. Drive > space I have, but thats a heck of big hunk of dependency. You mean that

I finally got some time to implement a pair of options to upsc for listing all configured UPSes on a given upsd: http://boxster.ghz.cc/projects/nut/changeset?new=branches%2Fupsc_list%2Fclients%2Fupsc.c%40859&old=trunk%2Fclients%2Fupsc.c%40821 http://boxster.ghz.cc/projects/nut/browser/branches/upsc_list/clients/upsc.c?rev=859 I think this should work with the new functions for parsing IPv6

On Tuesday 21 October 2014 22:06:48 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: > >> configure: error: libgd not found, required for CGI build > >> > >> And gdlib does not appear to be available from the repo's. > > Sorry, I must have missed that message.

On Jul 13, 2010, at 6:59 PM, Arnaud Quette wrote: > Author: aquette > Date: Tue Jul 13 22:59:52 2010 > New Revision: 2472 > URL: http://trac.networkupstools.org/projects/nut/changeset/2472 [...] > Modified: branches/AsciiDoc/docs/Makefile.am > = > = > = > = > = > = > = > = > ====================================================================== > ---

I need to install asciidoc on my build machine. There is a version for CentOS-5 available at dags rpm site. I have a repository configured for dag like so: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/ baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt