> Hi guys, > > my opinion is not to submit root packages in debian. The reason? It's a > lot of work and none of us have so much time to do this. I think it's > better > to leave root debian packages in the CERN repository. Actually packages > are > only for unstable release, but probably we can add also Ricardo's ones, > since > they are for the stable release.
I see no problem in that. Distributing the packages for stable in a more centralized way would make more sense than having separate repositories. This is a really good idea. I would be willing to maintain the packages and the upload them to the CERN repository. > > Just a question Ricardo: i see compiling root 5.32 I have problem > related to > xrootd, that's not anymore included in root. Did you disable this option > during configuration procedure? No, it's not disabled. I solved this by using the script installXrootd.sh in debian/rules to download, build and then package xrootd. Ricardo > > Cheers, > > Antonio > > > On Wednesday 11 January 2012 15:39:22 Ricardo Yanez wrote: >> > On Tue, Jan 10, 2012 at 8:14 PM, Ricardo Yanez >> <[email protected]> >> > >> > wrote: >> >>> On Tue, Jan 10, 2012 at 09:02:31AM -0800, Ricardo Yanez wrote: >> >>>> >> No, I cannot commit the time to be an active maintainer. At >> most >> >>>> >> >>>> I >> >>>> >> >>>> >> could >> >>>> >> commit to maintain a version for Debian stable. >> >>> >> >>> I wonder from where you obtained the experience that unstable is >> to >> >>> dynamic and the maintenance effort would be to large for your time >> >>> limit. Â Every package in Debian goes to unstable first (or >> >>> experimental) >> >>> as an exception. Â That's the usual way any package comes to >> Debian. >> >>> >> >>> Whether a package needs maintenance effort or not depends more >> from >> >>> the >> >>> package itself rather than a frequently changing unstable. Â What >> >>> exact >> >>> changes do you expect which would influence your packages. >> >> >> >> I do maintain packages on the side. It does depend to a large >> extend >> >> on >> >> the software itself. So, fair enough, I could give it a try, >> unstable, >> >> and work from there. How should I proceed? >> >> >> >> Ricardo >> > >> > Do you have a git repro or something like this ? >> > >> > I could help if you want, first step I think will be to get clhep2 >> > compile and working on all arch >> >> Sorry folks. It's piling up pretty quickly as I suspected. I pass. >> >> Ricardo >> >> > Bastien >> > >> >>>> In that case the packages are fine where they are (in my >> repository) >> >>>> and >> >>>> anybody is welcome to use them. >> >>>> >> >>>> I could accept uploads of other architectures if someone has the >> >>>> machine >> >>>> and is willing to compile. >> >>> >> >>> If you ask me this plan is more time consuming than doing a proper >> >>> upload and enable the Debian Science team to provide help if >> needed. >> >>> >> >>> Kind regards >> >>> >> >>> Â Â Â Â Andreas. >> >>> >> >>> -- >> >>> http://fam-tille.de >> >>> >> >>> >> >>> -- >> >>> To UNSUBSCRIBE, email to [email protected] >> >>> with a subject of "unsubscribe". Trouble? Contact >> >>> [email protected] >> >>> Archive: http://lists.debian.org/[email protected] >> >> >> >> -- >> >> To UNSUBSCRIBE, email to [email protected] >> >> with a subject of "unsubscribe". Trouble? Contact >> >> [email protected] >> >> Archive: >> >> http://lists.debian.org/67d6c5ef9b68759895c527fbad6b2e53.squirrel@webmai >> >> l.calel.org >> > >> > -- >> > To UNSUBSCRIBE, email to [email protected] >> > with a subject of "unsubscribe". Trouble? Contact >> > [email protected] >> > Archive: >> > http://lists.debian.org/CAE2SPAbYD6yG5Ak3Ut7Be-CsTKwWb1Q8vW0MF=ZF1cd_scL8 >> > [email protected] > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
