Message: previous - next
Month: February 2012

Re: [trinity-devel] How to build one package component only

From: Kristopher John Gamrat <chaotickjg@...>
Date: Sat, 18 Feb 2012 20:07:40 -0500
On Saturday 18 February 2012 07:45:26 pm Darrell Anderson wrote:
> Every package has a doc directory containing the documentation files. How do I build only that directory as a mini package?

Depends on your package manager. If your package manager does not require you to build actual source code (e.g. C or C++), you should be able to have your build script convert the Docbook files and put those into a package. You'd of course need to make sure that the documentation is not included in the main package containing the actual binaries that run your desktop.

> Reason: All Trinity documentation is contained in Docbook files. DocBook is a markup language. Quanta Plus and Kate provide no mechanism to view the final result because all Docbook files have to be converted to another form for viewing.
> As I revise the various docbook files, I want to regularly view the results in a Trinity desktop. I want to do this quickly without building an entire package.

You should not have to build a package. As long as it can still get the variables from the system you're converting or viewing them on, it should not be a problem.

> Side note: Basically, this is the beginning of a discussion about creating an efficient Docbook editing environment, which I'll post to the wiki. If you have any experience or interest in the development side of Docbook then please feel welcome to help. You don't have to write or edit, just help set up the environment and I'll document the process for everybody --- but I need help getting there. :)

Kris Gamrat
Ark Linux webmaster