Text archives Help
- From: tom fogal <tfogal@sci.utah.edu>
- To: iv3d-users@sci.utah.edu
- Subject: [IV3D-USERS] Re: Packaging imagevis3d in debian
- Date: Thu, 08 Dec 2011 16:46:42 -0700
Mathieu Malaterre <mathieu.malaterre@gmail.com> writes:
>
I have started packaging imagevis3d for debian, see
>
http://bugs.debian.org/651470.
Great, thank you!
I actually had started this process before, but gave up when I realized
that there was no way to create a debian package without getting your
email address publicly posted on the web =(. Maybe you'd like to take
ownership of the bug (or at least close it as a duplicate?)?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530666
Also note there is a 'notdebian' directory in the root 'imagevis3d'
repository (the debian policy guides specifically discourage putting a
'debian' directory in the package's repository, but when the maintainer
== the developer that adds logistical pains for no gain... so I just
called it 'notdebian' ;).
>
I was able to remove all convenient copies of third party libs
>
without too much troubles.
Yeah... sorry it isn't as nice as, say, a ./configure --option. The
issue is windows and mac: we want to keep iv3d easy to build on those
systems, where there are no useful package managers. Input/thoughts
welcome; I'd really like to not have e.g. zlib in our repository, but
I don't see a way around it that doesn't make building on windows
hellish.
>
However there is one thing I could not figure out: where can I find
>
the source stable release ?
Yes, sorry, we haven't been making these unfortunately. I can start
doing so with the next release, which will be 2.1.0.
We do build nightly tarballs. I don't want the URI they are at to get
crawled/archived via the web, but I will happily point you or anyone
that asks at them via a private mail.
>
I have based my debian package from svn rev :
>
>
URL: https://gforge.sci.utah.edu/svn/imagevis3d
>
Repository Root: https://gforge.sci.utah.edu/svn/imagevis3d
>
Repository UUID: c36c8488-0289-0348-9b64-b301f74bd9a7
>
Revision: 1729
>
>
Is there a page which explains which svn rev match release 2.0.1 ?
Unfortunately, no. I have all of that history in my local git
repositories, so I can tell you that 2.0.1 was built from imagevis3d
revision 1672, tuvok revision 1879, basics revision 153, and scio
revision 1623. Due to the svn:externals setup, I think/hope you can
just check out imagevis3d r1672 and it will grab all the appropriate
versions of everything.
>
For anyone interested, debian/* files are at:
>
>
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/imagevis3d/trunk/
>
>
or
>
>
svn co svn://svn.debian.org/svn/debian-med/trunk/packages/imagevis3d/trunk
Wonderful, thanks!
Could you take a look at the files in notdebian/ and see if there
any differences worth propagating to yours? One thing I will note
in particular is that you want to build the debian version with
PACKAGE_MANAGER defined. We have our own built-in updating mechanism,
but if the user gets IV3D through the package manager we of course want
to let the package manager control updates. That define disables our
built-in mechanism.
Let me know when you've done that; I'll probably want to steal your
versions of the debian files for notdebian/ at that point.
Thanks again!
-tom
Archive powered by MHonArc 2.6.16.