Re: [tei-council] Update on build problems with P5

There are also deb packages for the stylesheets. I know the Jenkins machines both have the deb packages installed; and I have them installed myself on my machines. Having them enables you to do teitorng myodd.odd at the command line and similar; it's very handy if you get used to it. When we switched the Jenkins build over to using the local copy of the Stylesheets from the repo, it was partly with the idea that we wanted to remove the dependency on having the installed deb packages (the other reason was that we wanted to build with the latest-and-greatest stylesheets, to avoid horrible build-update-build cycles when both the Stylesheets and P5 were changing frequently). So I think it would be possible to remove them from the build process; and I also know that we can't actually do a release of them without Sebastian, because he's the maintainer with the signing key. But I wouldn't be surprised if there are side-effects from removing them from the build, and perhaps also protests from people who are using them. If we can continue to build them without errors, we can at least focus on the problem of releasing them and not worry for the moment about whether it's easy to disentangle the rest of the infrastructure from them, for the moment. Cheers, Martin On 15-08-31 01:36 PM, Kevin Hawkins wrote:

I believe this is something that Sebastian set up:

http://wiki.tei-c.org/index.php/TEIDebian

He always advertised these as unofficial.

--Kevin

On 8/31/15 3:21 PM, Hugh Cayless wrote:

...

I honestly don’t even know what they’re for. Do people use them?

...

On Aug 31, 2015, at 16:04 , Martin Holmes wrote:

HI all,

Hugh and I have been wrestling with the very puzzling results of the P5 build on Jenkins: while TEIP5-Documentation works as expected, generating Guidelines based on the git version, TEIP5 seems to know nothing of git, and behaves as if we're still using svn.

I think I've figured out the cause. The Makefile* includes targets "debversion" and "deb" (the latter depends on the former), and the latter seems to be shot through with explicit references to svn:

@echo BUILD: make Debian tei-p5-database package (cd debian-tei-p5-database; debclean;debuild -eXSL=${XSL} -eINJENKINS=${INJENKINS} --no-lintian -nc -b -i.svn -I.svn -uc -us)

The Documentation build does not try to build the deb packages, but the full P5 build calls:

make* VCS=git clean deb dist

and in the process of that happening, VCS is set back to svn somehow. If I call

make* VCS=git clean dist

everything works OK.

I know nothing about building debian packages, so this is a mystery to me. I don't mind learning about it, and people assure me that it's not complicated, but it might be more than I can do in a couple of weeks, at least with any confidence. Does anyone else have familiarity with building deb packages?

*I hate make.

Cheers, Martin -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived