Nexista Debian Package

I asked for help on the debian mentors list and was indeed helped! Jonathan wrote back:

IANADD and can’t upload for you, but I can give you some feedback to get it into shape for a sponsor. At the moment there are some severe problems with it:

You have three lintian warnings because you haven’t used your full name as the maintainer and in the changelog, and because your tag line in the changelog doesn’t match your name and email in your debian/control file.

You haven’t specified your ITP bug number in debian/changelog.

debian/control: you should be working to standards version 3.8.0. See [1] for a checklist.

You should use your full name in debian/copyright (just as if you were making a legal assertion to it).

debian/README.Debian: again, use your full name.

debian/rules: get rid of comment cruft, like the fact that this is a sample script.

Your watch file doesn’t work [2].

These are fundamental problems and need fixing before a sponsor will consider your package. If you need help, you’re welcome to ask for it.

[1] /usr/share/doc/debian-policy/upgrading-checklist.txt
[2] man uscan

I won’t get to these issues until the next release of Nexista, but hopefully I’ll get it right then.

Releasing 0.2.4

Interest in PBooks is picking up, so I’m releasing a new point step for Nexista in the hopes that installing PBooks will get a little easier. This will also be a good exercise in automating the packaging process: dpkg, pear, and source!

I’ll have to push the LDAP query format off until the next release, but that won’t be too much of a problem for this release.

Source, pear, and debian packages are available here, and the pear package is also available via the pear.nexista.org pear channel.

pear: nexista-0.2.4.tgz
source: nexista-source-0.2.4.tgz
debian: php-nexista_0.2.4-1_all.deb

Checking for Extra Resources




This little shell script came in handy today:

grep 'query' ./sitemap.xml | awk '{ print $2}' | sort | uniq

I used to to list all the queries in my sitemap.xml file. With that information, I was able to compare it with a list of files in my query directory.

Why did I want to do this? I wanted to make sure that the queries I had were all being used. I had thought there was a possibility that I had stopped using a file, but not removed it from the repository. I had not in fact, so that is good!

Mailing Lists

Following the steps taken to support the PBooks project community, I’m setting up mailing lists for Nexista.

Nexista Mailing Lists

Caching Components




I’ve always output the results from XSLT without performing more operations. Now I’m thinking it might be a good idea to do some XML manipulation, which could leverage cached XML nodes which are repeatedly transformed with the same result. For example - menus, headers, footer, and the like.

XML parsers can usually add nodes with trees quite easily, so I be it would be faster (though more complicated) to go that route. Its at least worth a little experimentation, right?

The only major hurdle I see at this point is that I output to HTML, which is not valid XML. I’d have to first output to XML, then modify the result tree, then transform again to HTML. Eh, might not be worth it….