| === _thumper_ is now known as thumper | ||
| === imperius1 is now known as imperius1_away | ||
| === Israphel_ is now known as Israphel | ||
| === t1 is now known as tomer | ||
| === mimir|zZz is now known as mimir|on | ||
| === rgreening_ is now known as rgreening | ||
| === jarlen_ is now known as jarlen | ||
| G__81 | hi everyone | 16:08 |
|---|---|---|
| G__81 | pleia2, did you have a chance to look at my mail ? | 16:09 |
| === mimir|on is now known as mimir|afk | ||
| G__81 | anyone here ? | 17:19 |
| G__81 | hi pleia2, | 17:19 |
| jdbrowne | Hello, I would like to distribute a script and some data files to my colleagues (we already have a deb repository). It seems the best solution is cdbs with its makefile class and I write a simple makefile with "clean", "all", "check", "install". Does it sound fine? | 17:46 |
| maxb | I would say using cdbs in that case would be extreme overcomplexity | 17:50 |
| maxb | I would use plain debhelper | 17:50 |
| pleia2 | G__81: sorry, am at work at the moment, catch up later? | 17:56 |
| jdbrowne | maxb: ok, the docs all seems daunting for a simple script. | 18:03 |
| maxb | Trust me cdbs is even more daunting | 18:03 |
| jdbrowne | I trust you, I am reading https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/basic-debhelper.html | 18:04 |
| kklimonda | 6.10? :) | 18:05 |
| jdbrowne | The requested URL /9.04/ubuntu/packagingguide/C/basic-debhelper.html was not found on this server. | 18:06 |
| jdbrowne | I tried | 18:06 |
| kklimonda | it's a bit outdated but i think it should cover basics just fine.. | 18:07 |
| jdbrowne | MMmh, "apt-get source hello-debhelper" can't find a source package | 18:08 |
| G__81 | pleia2, yeah sure | 18:08 |
| maxb | jdbrowne: Are you aware of dh-make? | 18:08 |
| maxb | It generates you a template debhelper packaging | 18:08 |
| jdbrowne | I used dh-make at some point following the debian maintainer guide but it was heavily oriented toward source package that I thought it was not the right tool for a script | 18:11 |
| maxb | The only difference is that instead of ./configure and make, you're just directly installing files that are shipped in the package | 18:14 |
| jdbrowne | so I just need an install target in a makefile? | 18:14 |
| maxb | You don't even need a makefile | 18:17 |
| maxb | You can just write commands that install your files directly in the debian/rules file, if the package is that simple | 18:17 |
| jdbrowne | I thought the "rules" files was meant to create a package not install the file in the location I need them to be. | 18:19 |
| jdbrowne | I am back at reading https://wiki.ubuntu.com/PackagingGuide/Complete#rules and it is clearer now | 18:19 |
| jdbrowne | I am going to edit the "rules" file that was created by dh_make and customize it. | 18:21 |
| jdbrowne | What is the convention over the target which ends with '-stamp' like build-stamp and configure-stamp? | 18:27 |
| jdbrowne | ok, I get it makes phony targets not phony anymore | 18:30 |
| === micahg1 is now known as micahg | ||
| jdbrowne | what does dpkg-buildpackage do with the "install" target of the debian/rules file? My guess is that it does not execute this target because it is not dpkg-buildpackage's role to install th script. | 18:42 |
| kklimonda | jdbrowne: it installs package in temp directory (by default debian/tmp/ afair) | 18:46 |
| jdbrowne | maxb: the way the debhelper has written the debian/rules, I think it expects a makefile, and I think it expects a makefile which knows about the DESTDIR directory | 18:47 |
| maxb | yes | 18:47 |
| maxb | But nothing says you have to leave it that way | 18:47 |
| jdbrowne | this is tricky, actually, you do execute the upstream makefile but you succeed to fake the makefile only if you know how to ask the upstream makefile to change the installation directory... well anyway, I think I begin to get it. Where are all those convention about DESTDIR and such specified? in the Debian Policy? | 18:49 |
| maxb | Why do you even have a Makefile? I thought you said you just had a bunch of scripts? | 18:50 |
| jdbrowne | either I rewrite the debian/rules, or i re-use the debian/rules to the maximum without touching it and write an upstream makefile. At some point, I will apply my newly packaging skills to source package too. I guess it make sense making the debian/rules look alike | 18:52 |
| maxb | http://jabberwock.vm.bytemark.co.uk/~maxb/example-package-1/ | 18:53 |
| maxb | ^ There is a truly trivial example package for you which simply installs a /usr/bin/myscript which says "Hello world!" | 18:54 |
| jdbrowne | this is precious thank you | 18:54 |
| pace_t_zulu | hi guys... i am trying to create a debdiff to provide to patch launchpad bug #301007 | 19:16 |
| pace_t_zulu | I have modified the source | 19:17 |
| pace_t_zulu | i ran 'dch -i' | 19:17 |
| pace_t_zulu | to update the changelog | 19:17 |
| pace_t_zulu | i am following this guide: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff | 19:17 |
| pace_t_zulu | the current version of the package is ubuntu3 ... i have been able to create the ubuntu4.dsc from which the debdiff will be created | 19:18 |
| pace_t_zulu | can someone help me with this? | 19:18 |
| maxb | so..... now just run debdiff | 19:19 |
| pace_t_zulu | maxb: i do not have the ubuntu4.dsc from which i need to do it | 19:19 |
| maxb | You just said "i have been able to create the ubuntu4.dsc" | 19:20 |
| pace_t_zulu | maxb: apologies.. i was unable | 19:21 |
| maxb | This channel really isn't the right one, please transfer to #ubuntu-motu for packaging assistance, thanks! | 19:22 |
| pace_t_zulu | maxb: thank you | 19:23 |
| === mimir|afk is now known as mimir|om | ||
| === k00011 is now known as k0001 | ||
| === santiago-pgsql is now known as santiago-ve | ||
| === mimir|om is now known as mimir|on | ||
| === mimir|on is now known as mimir|zZz | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!