Re: Debhelper 7
just found this old message: Marius Vollmer wrote: > That's the magic. You will likely need to update Perl as well, and then > update many many Perl modules. This is what I have done for Harmattan, > and now I am sitting on about 100 packages that I have updated... :-) it is actually much less http://www.maemory.com/N900/perl5.10/ http://www.maemory.com/N900/libperl/ but running it in the SDK is a hassle (you need to move devkit perl away and fix all references) > You can also backport debhelper 7 to Perl 5.8. that's what I have done: http://www.maemory.com/N900/build/ you'll have to move away the dh_* files from your devkits otherwise it won't use the files from the package. You could also try the SDK+ based on scratchbox 2 http://maemo-sdk.garage.maemo.org/ which make it easy to use the host perl with export SBOX_REDIRECT_FORCE=/usr/bin/perl cheers, -- Thomas Tanner -- email: tan...@gmx.de GnuPG: 1024/5924D4DD ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
hi, I've a ported debhelper 7.3.15 to Maemo5 http://www.maemory.com/N900/build/debhelper_7.3.15maemo1_all.deb http://www.maemory.com/N900/README.txt happy new year! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Fri, Dec 18, 2009 at 9:46 AM, Eero Tamminen wrote: > ext Jussi Hakala wrote: >> You can also try the debian-squeeze devkit available from scratchbox.org. >> >> Note that this is not (yet) supported by Fremantle SDK and you need to >> create your scratchbox targets by hand instead of the installation script, >> but should be enough to allow you to use debhelper 7. > > But I think using something like that would require that Maemo > auto-builder supports it too... I wonder if it is possible to dynamically select different devkits from inside a target (using some SBOX_* environment variable), just like it's possible for selecting a different compiler ? I've managed to do something similar (using the SBOX_SCRATCHBOX_CONFIG as documented on /scratchbox/doc/variables.txt) to dynamically change compilers without requiring to change the target configuration, but I don't know if tha's possible for devkits too. If that would at all be possible, it would just be a matter of having the devkits installed on the autobuilder, without changing the target setup. My two cents, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
Hi, ext Jussi Hakala wrote: > ext Anderson Lizardo wrote: >> Now things might get complex if the packaging already uses some new >> features of level 7, like those CDBS-like helper rules. In such cases, >> looking at versions prior to the compatibility level upgrade might >> help doing the downgrade (and most Debian packages are kept in public >> SCMs like svn.debian.org). > > You can also try the debian-squeeze devkit available from scratchbox.org. > > Note that this is not (yet) supported by Fremantle SDK and you need to > create your scratchbox targets by hand instead of the installation > script, but should be enough to allow you to use debhelper 7. But I think using something like that would require that Maemo auto-builder supports it too... - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
ext Anderson Lizardo wrote: > Now things might get complex if the packaging already uses some new > features of level 7, like those CDBS-like helper rules. In such cases, > looking at versions prior to the compatibility level upgrade might > help doing the downgrade (and most Debian packages are kept in public > SCMs like svn.debian.org). You can also try the debian-squeeze devkit available from scratchbox.org. Note that this is not (yet) supported by Fremantle SDK and you need to create your scratchbox targets by hand instead of the installation script, but should be enough to allow you to use debhelper 7. Additionally, the devkit is a lot smaller, so the number of packages it "shadows" is much less. For example, stuff like cdbs is solely left for target as they properly should be. Regards, Jussi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
ext Yves-Alexis Perez writes: > On 16/12/2009 09:33, Marius Vollmer wrote: >> (The main thing missing from debhelper IMO is better support for -dbg >> packages.) > > Hmmh, what exactly do you need? Because with the tiny.rules, the only > thing needed is the -dbg package declared in debian/control (dh_install > takes care of everything). Does it? I have to try harder, then. I always need to put things like this into my debian/rules to get non-empty -dbg packages: override_dh_strip: dh_strip -plibgq-gconf0 --dbg-package=libgq-gconf0-dbg dh_strip Time to have a look at the debhelper docs again... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On 16/12/2009 09:33, Marius Vollmer wrote: > (The main thing missing from debhelper IMO is better support for -dbg > packages.) Hmmh, what exactly do you need? Because with the tiny.rules, the only thing needed is the -dbg package declared in debian/control (dh_install takes care of everything). Though I don't have (source) packages with more than one (binary) -dbg package. Cheers, -- Yves-Alexis signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On 16/12/2009 08:12, Rémi Denis-Courmont wrote: > On Tuesday 15 December 2009 22:10:39 ext Jeremiah Foster, you wrote: >>> * debian/compat: 7 -> 5 >>> * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5) >>> * And maybe comment out a few dh_* calls from debian/rules, which >>> might not exist on level 5 >> >> One of the huge advantages of moving to debhelper 7 compat is that you can >> have your debian/rules files look like this: >> >> #!/usr/bin/make -f >> %: >> dh $@ >> >> Simple. You pass everything off to debhelper. > > That takes care of the packaging part, but not the building part or does it? > AFAICT, if you really want short and implicit rules, you could use CDBS. That > works fine with any debhelper from version 4 and up. > That's not exactly the place to do a cdbs vs. debhelper debate, but (with my debian hat on) I really prefer using debhelper 7 with override stuff than cdbs. It's really easier to fine-tune. Is there a reason why scratchbox is stuck with etch base system? In Debian we usually build packages for unstable using unstable. I can understand the distro hasn't exactly the same purposes, and that tracking unstable would be too much work, but why not at least upgrading too Lenny (which has debhelper 7, though not the version with dh_override_*) Cheers, -- Yves-Alexis signature.asc Description: OpenPGP digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
"Denis-Courmont Remi (Nokia-D/Helsinki)" writes: > On Tuesday 15 December 2009 22:10:39 ext Jeremiah Foster, you wrote: >> > * debian/compat: 7 -> 5 >> > * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5) >> > * And maybe comment out a few dh_* calls from debian/rules, which >> > might not exist on level 5 >> >> One of the huge advantages of moving to debhelper 7 compat is that you can >> have your debian/rules files look like this: >> >> #!/usr/bin/make -f >> %: >> dh $@ >> >> Simple. You pass everything off to debhelper. > > That takes care of the packaging part, but not the building part or > does it? It also takes care of building. Check the documentation of the "Build system options" in man debhelper and look into /usr/share/perl5/Debian/Debhelper/Buildsystem. The "dh" program itself is a simple sequencer that runs a score of dh_* utilities in the right order, including the new dh_auto_configure, dh_auto_build, and dh_auto_install. These dh_auto_* utiltities can recognize a number of buildsystems, like autotools, Makefile.PL, setup.py, etc. > AFAICT, if you really want short and implicit rules, you could use CDBS. That > works fine with any debhelper from version 4 and up. It's a matter of taste, I guess. I personally find cdbs impenetrable, what with the million variables that you need to set. Debhelper really doesn't need to be wrapped up to make it easy. (The main thing missing from debhelper IMO is better support for -dbg packages.) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Tuesday 15 December 2009 22:10:39 ext Jeremiah Foster, you wrote: > > * debian/compat: 7 -> 5 > > * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5) > > * And maybe comment out a few dh_* calls from debian/rules, which > > might not exist on level 5 > > One of the huge advantages of moving to debhelper 7 compat is that you can > have your debian/rules files look like this: > > #!/usr/bin/make -f > %: > dh $@ > > Simple. You pass everything off to debhelper. That takes care of the packaging part, but not the building part or does it? AFAICT, if you really want short and implicit rules, you could use CDBS. That works fine with any debhelper from version 4 and up. -- Rémi Denis-Courmont Nokia Devices R&D, Maemo Software, Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Dec 14, 2009, at 14:02, Anderson Lizardo wrote: > On Mon, Dec 14, 2009 at 7:15 AM, Marius Vollmer > wrote: >> On balance, I think it is better to just stick to debhelper 5 in >> Fremantle. > > And from our experience in PyMaemo backporting various (but not that > many) packages from debhelper compatibility level 7 to 5, in most > cases you need just to change: > > * debian/compat: 7 -> 5 > * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5) > * And maybe comment out a few dh_* calls from debian/rules, which > might not exist on level 5 One of the huge advantages of moving to debhelper 7 compat is that you can have your debian/rules files look like this: #!/usr/bin/make -f %: dh $@ Simple. You pass everything off to debhelper. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Mon, Dec 14, 2009 at 7:15 AM, Marius Vollmer wrote: > On balance, I think it is better to just stick to debhelper 5 in > Fremantle. And from our experience in PyMaemo backporting various (but not that many) packages from debhelper compatibility level 7 to 5, in most cases you need just to change: * debian/compat: 7 -> 5 * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5) * And maybe comment out a few dh_* calls from debian/rules, which might not exist on level 5 Now things might get complex if the packaging already uses some new features of level 7, like those CDBS-like helper rules. In such cases, looking at versions prior to the compatibility level upgrade might help doing the downgrade (and most Debian packages are kept in public SCMs like svn.debian.org). Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
ext Teemu Ikonen writes: > [...] Do you have any specific idea on why debhelper 7 does not run on > Fremantle SDK (I suppose there's no need to run it on the device)? Is > there any chance at all to get it working, by upgrading perl or some > other magic? Yes, there is a chance, but it is not pretty. The Fremantle SDK, like all versions of the Maemo SDK, uses Scratchbox with a specific set of devkits. One of the devkits is the debian-etch one, and that devkit contains debhelper. The nature of devkits is that they shadow whatever is in the target. Thus, installing debhelper 7 in the target doesn't do anything: you will still get the debhelper from the devkit. You would either have to update the devkit itself, or somehow disable it while building your package only. You can disable the devkits with a snippet like this in debian/rules: # Sanitize build environment when running inside Scratchbox 1 ifneq (,$(wildcard /targets)) export SBOX_REDIRECT_TO_DIRS= export PATH=/scratchbox/compilers/bin:/bin:/usr/bin:/scratchbox/tools/bin endif This is a hack, and you have to assume responsibility for all the fall-out that it produces. :) That's the magic. You will likely need to update Perl as well, and then update many many Perl modules. This is what I have done for Harmattan, and now I am sitting on about 100 packages that I have updated... :-) You can also backport debhelper 7 to Perl 5.8. On balance, I think it is better to just stick to debhelper 5 in Fremantle. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Mon, Nov 30, 2009 at 8:48 AM, Marius Vollmer wrote: > ext Teemu Ikonen writes: >> There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, >> but trying to compile it in the SDK fails miserably. The problem seems >> to be related to perl, which is also of similar vintage (i.e. >> obsolete) in the SDK. > > Yeah, everything in maemo-pkg is meant for Harmattan. I will update the > description. Good to know. Do you have any specific idea on why debhelper 7 does not run on Fremantle SDK (I suppose there's no need to run it on the device)? Is there any chance at all to get it working, by upgrading perl or some other magic? Best, Teemu ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
ext Teemu Ikonen writes: > There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, > but trying to compile it in the SDK fails miserably. The problem seems > to be related to perl, which is also of similar vintage (i.e. > obsolete) in the SDK. Yeah, everything in maemo-pkg is meant for Harmattan. I will update the description. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Sat, Nov 28, 2009 at 4:43 PM, Jeremiah Foster wrote: > > On Nov 28, 2009, at 16:00, Teemu Ikonen wrote: >> You can check out the sources by doing >> git clone git://gitorious.org/maemo-pkg/debhelper.git >> But, as said, the build fails. > > I know that Nokia sort of disables perl on the device - they might do that on > the SDK as > well. Have you installed the perl-moduels package as well as perl-base in the > SDK? Yes, I have the up to date versions of these. Anyway, this is a maemofied source package, so the dependencies (with correct versions) should be listed in the debian/control file. The build fails with: $ fakeroot debian/rules binary ./run dh binary Unknown option: w dh: unknown option; aborting Since dh is a perl script, it would seem that perl in the SDK lacks some feature it needs. I'm clueless with perl though, so I cannot say where it actually fails. Teemu >>> Teemu Ikonen wrote: >>>> Hi, >>>> >>>> I'm trying to compile / port some C libraries from Debian to Maemo 5. >>>> The actual compilation goes without problems, but the packaging >>>> scripts use the (very nice) command sequencer functionality of >>>> debhelper v. 7, while the SDK has only debhelper 5. > > This is excellent - I would love to see this in maemo because it makes the > rules files so simple. > >>>> >>>> There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, >>>> but trying to compile it in the SDK fails miserably. The problem seems >>>> to be related to perl, which is also of similar vintage (i.e. >>>> obsolete) in the SDK. >>>> >>>> Has anyone else tried or managed to get debhelper 7 running on maemo >>>> 5? Having to rewrite the packaging on every library I need would be a >>>> major suck. >>>> >>>> Teemu > > Let me know how I can help. Perhaps post your error message here when > building? > > Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Nov 28, 2009, at 16:00, Teemu Ikonen wrote: > On Sat, Nov 28, 2009 at 3:02 PM, David Greaves wrote: >> Do you have a URL for the .dsc and tarball > > You can check out the sources by doing > git clone git://gitorious.org/maemo-pkg/debhelper.git > > But, as said, the build fails. I know that Nokia sort of disables perl on the device - they might do that on the SDK as well. Have you installed the perl-moduels package as well as perl-base in the SDK? > > Teemu > >> Teemu Ikonen wrote: >>> Hi, >>> >>> I'm trying to compile / port some C libraries from Debian to Maemo 5. >>> The actual compilation goes without problems, but the packaging >>> scripts use the (very nice) command sequencer functionality of >>> debhelper v. 7, while the SDK has only debhelper 5. This is excellent - I would love to see this in maemo because it makes the rules files so simple. >>> >>> There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, >>> but trying to compile it in the SDK fails miserably. The problem seems >>> to be related to perl, which is also of similar vintage (i.e. >>> obsolete) in the SDK. >>> >>> Has anyone else tried or managed to get debhelper 7 running on maemo >>> 5? Having to rewrite the packaging on every library I need would be a >>> major suck. >>> >>> Teemu Let me know how I can help. Perhaps post your error message here when building? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Sat, Nov 28, 2009 at 3:02 PM, David Greaves wrote: > Do you have a URL for the .dsc and tarball You can check out the sources by doing git clone git://gitorious.org/maemo-pkg/debhelper.git But, as said, the build fails. Teemu > Teemu Ikonen wrote: >> Hi, >> >> I'm trying to compile / port some C libraries from Debian to Maemo 5. >> The actual compilation goes without problems, but the packaging >> scripts use the (very nice) command sequencer functionality of >> debhelper v. 7, while the SDK has only debhelper 5. >> >> There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, >> but trying to compile it in the SDK fails miserably. The problem seems >> to be related to perl, which is also of similar vintage (i.e. >> obsolete) in the SDK. >> >> Has anyone else tried or managed to get debhelper 7 running on maemo >> 5? Having to rewrite the packaging on every library I need would be a >> major suck. >> >> Teemu >> ___ >> maemo-developers mailing list >> maemo-developers@maemo.org >> https://lists.maemo.org/mailman/listinfo/maemo-developers > > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
In such cases I usually get the packaging patch from the previous Debian version, they usually don't change much. Regards: Bundyo - Original message - > Hi, > > I'm trying to compile / port some C libraries from Debian to Maemo 5. > The actual compilation goes without problems, but the packaging > scripts use the (very nice) command sequencer functionality of > debhelper v. 7, while the SDK has only debhelper 5. > > There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, > but trying to compile it in the SDK fails miserably. The problem seems > to be related to perl, which is also of similar vintage (i.e. > obsolete) in the SDK. > > Has anyone else tried or managed to get debhelper 7 running on maemo > 5? Having to rewrite the packaging on every library I need would be a > major suck. > > Teemu > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
Do you have a URL for the .dsc and tarball David Teemu Ikonen wrote: > Hi, > > I'm trying to compile / port some C libraries from Debian to Maemo 5. > The actual compilation goes without problems, but the packaging > scripts use the (very nice) command sequencer functionality of > debhelper v. 7, while the SDK has only debhelper 5. > > There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, > but trying to compile it in the SDK fails miserably. The problem seems > to be related to perl, which is also of similar vintage (i.e. > obsolete) in the SDK. > > Has anyone else tried or managed to get debhelper 7 running on maemo > 5? Having to rewrite the packaging on every library I need would be a > major suck. > > Teemu > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Debhelper 7
Hi, I'm trying to compile / port some C libraries from Debian to Maemo 5. The actual compilation goes without problems, but the packaging scripts use the (very nice) command sequencer functionality of debhelper v. 7, while the SDK has only debhelper 5. There is an up-to-date 'maemofied' debhelper in maemo.gitorious.org, but trying to compile it in the SDK fails miserably. The problem seems to be related to perl, which is also of similar vintage (i.e. obsolete) in the SDK. Has anyone else tried or managed to get debhelper 7 running on maemo 5? Having to rewrite the packaging on every library I need would be a major suck. Teemu ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
