Kjetil Kjernsmo wrote:
On Wednesday 08 October 2008 17:15:50 Tim Haynes wrote:
I'm wondering how you've gone about it; I saw the mention of
http://debianpaket.de/svn-buildpackage/index.html a while ago but have I
missed an actual control file in the mails? Could I have a copy and play
with it here?
No, I didn't post it, but please find it attached. I took the description from
one of your web pages, but made it a bit less marketish. :-)
I think I have the build-deps correct now.
Thanks for this. Good news: I have a build env here where I ran dh_make
within a build-directory, copied your control file into place and it
successfully built a ../virtuoso-opensource_5.0.9-rc6-1_i386.deb.
One obvious bug: we need to sort out --with-layout, as the above process
erroneously creates a /usr/var/lib/... structure.
I'll look into that tomorrow, but meanwhile, do you have a debian/rules
file to go with that control file, so I can see how yours differs from
dh_make's default output?
[]
I figured since this is quite easy, and my packages are not in such a good
shape, so it might be better to start from scratch and possibly create a
debian/ directory in the CVS. My package would then only be a diversion from
this.
My aim, currently, is to produce a debian/* set of files (mostly rules &
control) that can be incorporated in the primary CVS repository. One of our
other open-source projects, iODBC, does this, with fair success.
I'm also thinking, in the absence of a designated DD just yet, it would be
wise for the maintainer information to be set to "OpenLink Virtuoso
Maintainer" and "vos.admin @ openlinksw.com".
init-scripts are not hard to write. Debian packages an /etc/init.d/skeleton
file that you can copy and tweak; all Virtuoso requires is that you cd to
the directory containing virtuoso.ini and run virtuoso-t there.
Ah, OK! Actually, I found a debian/init.d.ex too.
That would also do nicely. It'll take a bit of hacking working from the
init.d.ex; will have to resolve the way the PIDFILE works, etc.
This will
then create the empty database; the first time you run it, it loads a bunch
of *.vad packages into the database (so you might want a warning "please
wait a while" - compare openssh-server generating keys the first time
around).
This should perhaps be done when first configuring virtuoso in the install
process?
Ultimately we could seek to use debconf for it; "Would you like to install
the Conductor in this instance? How about the ODS application suite?" etc.
That won't happen tomorrow, though!
It might also help to specify ./configure --with-layout=debian so
it uses /var/lib/virtuoso/ as the database directory.
That's a nice feature! It can be added to debian/rules but perhaps there are
better ways of doing it too?
AFAIK that would be the best way - when on debian, etc.
Thanks,
~Tim
--
Tim Haynes
Product Development Consultant
OpenLink Software
<http://www.openlinksw.com/>
