Re: Debian Packages

From: Christian Holm Christensen <cholm_at_nbi.dk>
Date: Thu, 09 Jun 2005 15:55:44 +0200


Hi Fons,

On Wed, 2005-06-08 at 07:53 +0200, Fons Rademakers wrote:
> Hi Antonio and Christian,
>
> can you
> agree on a fix and mail me a patch?

It's really quite simple, in the file
`build/package/lib/makebuilddepend.sh', change the lines

            *asimage)   echo -n ", AfterStep-devel"                     ;;
and
        *asimage)       echo -n ", libafterimage-dev"                   ;;

to

  #           *asimage)   echo -n ", AfterStep-devel"                     ;;
            *asimage)                        ;;

and

  #        *asimage)       echo -n ", libafterimage-dev"                   ;;
          *asimage)                         ;;

That's it.

> > Many thanks for your message.
> > Let me be clear that I do not have any idea of maintaining the deb
> > packages for root.

I still maintain, that it would be best if Fons would set up a Debian machine and build the packages as part of the release process. After all, Fons is the one who knows when releases take place. And after all, it's straight forward to do. And of course similar for the RPMs.

> However, since I think that they constitute an
> > immense repository of "software" wisdom, I humbly try to get science
> > students to have just a crude idea of how powerful they can be by having
> > them on a live system that they can try and install very easily on their
> > computers.
> > As you said PAIPIX is based on knoppix that is not vanilla Debian and
> > therefore should not be used as default to build the root debian
> > packages but rather as "double check" that everything is working fine.

I agree. The best place to build the Debian GNU/Linux packages, is on a Debian GNU/Linux (sarge) system. Now, whether it's a standalone machine, or a UML machine doesn't really matter.

> > My only purpose is rather to try to help the root "make debian" to be as
> > powerful and complete as possible.
> > I would be happy to pick the compiled debian packages from an existing
> > repository. However, it should be complete. My compilation includes the
> > following packages that include much more than what is available in the
> > repository that you have mentioned.
> > These packages were produced by getting the code form cvs head (today)
> > as you suggested :
> > cvs -z3 checkout -r HEAD root
> > and correcting the
> > 1 - the libafterimage-dev dependency in the
> > build/package/lib/makebuilddepend.sh file. (We are almost there.)
> > 2 - Another subsisting problem is that the debian/rules for cleaning
> > remove the test/Makefile which is necessary to build the examples in the
> > test directory. This makefile does not get installed and I think it should.

The test/Makefile is removed as part of cleaning the source tree, as it is remade at configure time. In fact, ROOT should not distribute this file from CVS (as config/Makefile.config isn't either). Whether to include the Makefile in the distribution can be discussed. The generated Makefile contains hooks ment for the source tree, and are really not valuable out side of the source tree.  

> > The obtained packages are:

[edited the list a bit - hard to read]

        libroot_5.01.01-1_i386.deb 
        root-bin_5.01.01-1_i386.deb             
        root-cint_5.01.01-1_i386.deb            
        root-doc_5.01.01-1_all.deb              
        root-plugin-asimage_5.01.01-1_i386.deb 
        root-plugin-fumili_5.01.01-1_i386.deb   
        root-plugin-gl_5.01.01-1_i386.deb       
        root-plugin-hbook_5.01.01-1_i386.deb    
        root-plugin-krb5_5.01.01-1_i386.deb     
        root-plugin-ldap_5.01.01-1_i386.deb     
        root-plugin-minuit_5.01.01-1_i386.deb   
        root-plugin-mlp_5.01.01-1_i386.deb
        root-plugin-mysql_5.01.01-1_i386.deb
        root-plugin-netx_5.01.01-1_i386.deb
        root-plugin-pgsql_5.01.01-1_i386.deb
        root-plugin-proof_5.01.01-1_i386.deb
        root-plugin-pythia6_5.01.01-1_i386.deb
        root-plugin-python_5.01.01-1_i386.deb
        root-plugin-quadp_5.01.01-1_i386.deb
        root-plugin-xml_5.01.01-1_i386.deb
        root-proofd_5.01.01-1_i386.deb
        root-rootd_5.01.01-1_i386.deb
        root-xrootd_5.01.01-1_i386.deb
        root_5.01.01-1_all.deb                  
        ttf-root_5.01.01-1_all.deb

I get

        libroot-dev_5.01.01-1_i386.deb
        libroot_5.01.01-1_i386.deb
        root-bin_5.01.01-1_i386.deb
        root-cint_5.01.01-1_i386.deb
        root-doc_5.01.01-1_all.deb
        root-plugin-asimage_5.01.01-1_i386.deb
        root-plugin-castor_5.01.01-1_i386.deb
        root-plugin-chirp_5.01.01-1_i386.deb
        root-plugin-clarens_5.01.01-1_i386.deb
        root-plugin-dcache_5.01.01-1_i386.deb
        root-plugin-fumili_5.01.01-1_i386.deb
        root-plugin-gl_5.01.01-1_i386.deb
        root-plugin-hbook_5.01.01-1_i386.deb
        root-plugin-krb5_5.01.01-1_i386.deb
        root-plugin-ldap_5.01.01-1_i386.deb
        root-plugin-minuit_5.01.01-1_i386.deb
        root-plugin-mlp_5.01.01-1_i386.deb
        root-plugin-mysql_5.01.01-1_i386.deb
        root-plugin-netx_5.01.01-1_i386.deb
        root-plugin-oracle_5.01.01-1_i386.deb
        root-plugin-peac_5.01.01-1_i386.deb
        root-plugin-pgsql_5.01.01-1_i386.deb
        root-plugin-proof_5.01.01-1_i386.deb
        root-plugin-pythia5_5.01.01-1_i386.deb
        root-plugin-pythia6_5.01.01-1_i386.deb
        root-plugin-python_5.01.01-1_i386.deb
        root-plugin-qt_5.01.01-1_i386.deb
        root-plugin-quadp_5.01.01-1_i386.deb
        root-plugin-ruby_5.01.01-1_i386.deb
        root-plugin-sapdb_5.01.01-1_i386.deb
        root-plugin-venus_5.01.01-1_i386.deb
        root-plugin-xml_5.01.01-1_i386.deb
        root-proofd_5.01.01-1_i386.deb
        root-rootd_5.01.01-1_i386.deb
        root-xrootd_5.01.01-1_i386.deb
        root_5.01.01-1_all.deb
        ttf-root-installer_5.01.01-1_all.deb
        ttf-root_5.01.01-1_all.deb

The differences are

        root-plugin-castor_5.01.01-1_i386.deb
        root-plugin-chirp_5.01.01-1_i386.deb
        root-plugin-clarens_5.01.01-1_i386.deb
        root-plugin-dcache_5.01.01-1_i386.deb
        root-plugin-oracle_5.01.01-1_i386.deb
        root-plugin-peac_5.01.01-1_i386.deb
        root-plugin-pythia5_5.01.01-1_i386.deb
        root-plugin-qt_5.01.01-1_i386.deb
        root-plugin-ruby_5.01.01-1_i386.deb
        root-plugin-sapdb_5.01.01-1_i386.deb
        root-plugin-venus_5.01.01-1_i386.deb
        ttf-root-installer_5.01.01-1_all.deb
        

However, many of these requires non-standard Debian packages that I either made myself, or found on apt-get.org. Exceptions are qt, ruby, pythia5, and clarens. The castor packages requires a recent version of the CASTOR package (Debian packaging stuff should be part of upstream). For Oracle and SapDB, I used alien to translate the RPMs to Debian packages. For chirp, dcache, and venus, I made some packages myself.

Note, that this isn't the full ROOT installation possible. Still missing is Globus and AliEn support. Both of these packages are notoriously difficult to build. Both requires `boot-strapping' using it's own binary code - which is ridiculous for those kinds of packages. I've tried to make Debian packages of these packages, but gave up as I realised it would mean a major rewrite of the packages to do that.

Yours,

-- 
 ___  |  Christian Holm Christensen 
  |_| |  -------------------------------------------------------------
    | |  Address: Sankt Hansgade 23, 1. th.  Phone:  (+45) 35 35 96 91
     _|           DK-2200 Copenhagen N       Cell:   (+45) 24 61 85 91
    _|            Denmark                    Office: (+45) 353  25 404
 ____|   Email:   cholm_at_nbi.dk               Web:    www.nbi.dk/~cholm
 | |
Received on Thu Jun 09 2005 - 15:56:16 MEST

This archive was generated by hypermail 2.2.0 : Tue Jan 02 2007 - 14:45:09 MET