docbook-apps

Hello,

Of possible interest to the readers of this list:

https://so.nwalsh.com/2018/03/05/easy

(I found a couple of bugs so there’ll be updates within a day or two,
but I still think it might be of interest.)

Be seeing you,
norm

--
Norman Walsh <ndw@nwalsh.com> | Sun System & Network Admin manualIt is
http://nwalsh.com/ | important to realize that any lock can
| be picked with a big enough hammer.

I stopped at "you don't have to understand it" Norm?

... rude words.

I got as far as ant for builds. I can understand most of that.

Bash script... similar? Maybe

gradle? Wozzat.

Why make it deeper than needs be?

Dave




On 5 March 2018 at 15:34, Norman Walsh <ndw@nwalsh.com> wrote:
> Hello,
>
> Of possible interest to the readers of this list:
>
> https://so.nwalsh.com/2018/03/05/easy
>
> (I found a couple of bugs so there’ll be updates within a day or two,
> but I still think it might be of interest.)
>
> Be seeing you,
> norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | Sun System & Network Admin manualIt is
> http://nwalsh.com/ | important to realize that any lock can
> | be picked with a big enough hammer.



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

On 3/5/18 10:14 AM, Dave Pawson wrote:
> I got as far as ant for builds. I can understand most of that.
>
> Bash script... similar? Maybe
>
> gradle? Wozzat.
>
> Why make it deeper than needs be?

Dave,

The idea is to make it super easy for someone (e.g. an author) who just
wants to build the doc. They don't want to install a ton of stuff _at
the right version_ and keep track of it.

From an end-user's perspective, setting up the whole tool chain and
building the doc at most three steps:

# You only have to do this once (or use apt-get/yum or whatever windows
# users do to install software):
brew install gradle

# Get DocBook xml source from whatever source control system
# it lives in...
git clone <url-to-repo-for-somedoc> && cd somedoc

# This installs the DocBook toolchain and builds the doc:
gradle somedoc

Even as new versions of the underlying tools come out, "somedoc"
continues to build because your gradle file indicates what versions it
depends on. However, you easily can switch to newer versions if you need
to.

Regards,
David

Fair comment David.

Tempted to ask just how many are in that camp vs .... like us who do
odd things with docbook.
(for some defn of odd).

My position.
1. I don't stretch the schema (db simple would likely suffice)
2. I haven't updated my stylesheets in ages
3. I build html / pdf with svg ... (500k + words)
4. I want (need?) to validate as an option.
5. All files are on my hard drive

ant lets me pick / choose bits|all
Am I odd? Minority? Majority?

<quote src='@ndw'> Who needs steenkin
esisinternet </quote>

Sorry - that quote stuck from dsssl days Norm - bet you've forgotten it.

regards



On 5 March 2018 at 17:24, David Cramer <david@thingbag.net> wrote:
> On 3/5/18 10:14 AM, Dave Pawson wrote:
>>
>> I got as far as ant for builds. I can understand most of that.
>>
>> Bash script... similar? Maybe
>>
>> gradle? Wozzat.
>>
>> Why make it deeper than needs be?
>
>
> Dave,
>
> The idea is to make it super easy for someone (e.g. an author) who just
> wants to build the doc. They don't want to install a ton of stuff _at the
> right version_ and keep track of it.
>
> From an end-user's perspective, setting up the whole tool chain and building
> the doc at most three steps:
>
> # You only have to do this once (or use apt-get/yum or whatever windows
> # users do to install software):
> brew install gradle
>
> # Get DocBook xml source from whatever source control system
> # it lives in...
> git clone <url-to-repo-for-somedoc> && cd somedoc
>
> # This installs the DocBook toolchain and builds the doc:
> gradle somedoc
>
> Even as new versions of the underlying tools come out, "somedoc" continues
> to build because your gradle file indicates what versions it depends on.
> However, you easily can switch to newer versions if you need to.
>
> Regards,
> David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

On 3/5/18 11:33 AM, Dave Pawson wrote:
> ant lets me pick / choose bits|all
> Am I odd? Minority? Majority?

You are very odd Dave, but don't change the subject ;-)

In my case a couple of toolchain developers (minority) support a large
number of authors (majority). The tools developer's job is to make it so
the authors can create content without knowing much about the magic that
turns that into pdf/html/xml artifacts. A system for managing
dependencies like gradle+maven artifacts makes it easy to roll out
changes without breaking existing doc builds and to hide lots of
complexity from users.

Of course they need to understand enough to create correct markup, but
few if any of my authors will ever subscribe to this list, but they're
still DocBook users.

Regards,
David