[01:59] <Noskcaj> bdrung, slangasek, stgraber: Since you're the only dmb members online, would you mind checking the status of my MOTU application? It's been a week since i sent it and i've got more testimonials since.
[01:59] <slangasek> Noskcaj: not a member of the dmb
[02:00] <Noskcaj> sure? https://launchpad.net/~developer-membership-board/+mugshots
[02:43] <slangasek> Noskcaj: yes, quite sure that I am none of those people :)
[02:44] <Noskcaj> slangasek, Last time i click on the link you were there. Something in launchpad broke for me
[02:44] <slangasek> hah
[02:45] <Noskcaj> I'm going to guess it's because of the tech board
[02:45] <slangasek> I'm going to guess it's because of solar flares ;)
[02:48] <Noskcaj> :)
[07:38] <dholbach> good morning
[21:27] <MentalPower|Work> Hello again MOTU, I'm trying to create a two packages, a base nutcraker (that I already have) and a nutcracker-dbg with a few compile time debugging options (and debugging symbols) turned on. I've already found how to not strip the debugging symbols, but I have not found another package that uses different configure flags for different packages
[21:51] <Noskcaj> MentalPower|Work, Normally -dbg packages are made only as addons, with dh_strip --dbg-package= and maybe some extra files/links
[21:51] <MentalPower|Work> hmm... is there a way to have two compile chains without needing two sources?
[22:00] <Rhonda> Why would you want two compile chains?   Like Noskcaj mentioned, compile it once with debug symbols turned on, and use dh_strip --dbg-pkg
[22:00] <Rhonda> The regular package will then be without the debug symbols which get extracted to the mentioned package.
[22:01] <Rhonda> That's the way most packages do it.  Just look at the source package of a random -dbg package.
[22:35] <MentalPower|Work> Rhonda: I need to enable some compile-time debugging options
[22:35] <MentalPower|Work> this specific software doesn't do hardly any debugging output unless its compiled in
[22:40] <jtaylor> MentalPower|Work: a library or application?
[22:41] <jtaylor> for application just compile a second time, rename the binary (and its libraries if it has some) and install them in a dbg package
[22:41] <jtaylor> see e.g. python-dbg (conceptionally, don't look at the packaging ;) )
[22:42] <MentalPower|Work> application
[22:45] <MentalPower|Work> hmm... let me look at python
[22:50] <jtaylor> or fftw3
[22:50] <jtaylor> it builds multiple times with different configurations and sticks the results in different packages
[22:50] <jtaylor> packaging should be easier to understand than python, though its also not great
[22:50] <jtaylor> don't know of better examples
[22:55] <MentalPower|Work> jtaylor: you're right, python's packaging is all over the place. fftw's is a bit better, but I can't find where its doing the two compiles
[22:56] <jtaylor> MentalPower|Work: in build-arch:
[22:57] <jtaylor> multiple configure make install DESTDIR
[22:57] <jtaylor> the destdir is the important part
[22:57] <jtaylor> moving into packages is then using the --sourcedir argument of dh_install
[22:57] <jtaylor> in binary-arch:
[22:58] <jtaylor> the rest is just cludge because not all variants work on all arches
[22:59] <jtaylor> you hopefully won't need that
[23:37] <sontek> When you have two packages with same name but different versions, how do you know which one will be selected by apt-get
[23:37] <sontek> I just built a new package for precise that is updated from the ubuntu included version
[23:38] <sontek> This is what I see when I do show: http://paste2.org/xnCU2dJD
[23:48] <jtaylor> the one which has a higher version according to dpkg --compare-versions
[23:49] <jtaylor> but apt.preferences are taken into acount for automatic upgrades
[23:50] <jtaylor> sontek: ^
[23:50] <sontek> jtaylor: ok, that sounds fine then
[23:51] <sontek> Now I have one problem, there is one director in the .tar.gz that isn't being included right now
[23:51] <sontek> What defines what files get shipped?
[23:51] <sontek> I see the .install files
[23:51] <jtaylor> install files and "manual" copies in debian/rules
[23:51] <jtaylor> also .links .manpages etc