[16:28] <karstensrage> hello
[16:28] <karstensrage> reading this: http://packaging.ubuntu.com/html/packaging-new-software.html
[16:29] <karstensrage> seems pretty straight forward but im missing a piece of understanding
[16:29] <karstensrage> if im on a 12.04 ubuntu machine doing all this
[16:29] <karstensrage> how would the package work if it were run on 14,04?
[16:34] <Rhonda> Either out of the box, or you would need to compile it in a 14.04 environment new because of generated dependencies in the binary that aren't resolvable anymore on 14.04 from the 12.04 build
[16:36] <karstensrage> Rhonda, so the package i am dealing with is a PAM module (shared lib), which "depends" on another shared lib that i wrote... so that will be two separate packages, and the first depends on the 2nd right?
[16:36] <karstensrage> then the 2nd library depends on libxml2 and libssl
[16:37] <karstensrage> so even though the code i wrote isnt changing across 12.04 and 14.04, the libc, and other libs are changing right?
[16:38] <Rhonda> Yes.
[16:39] <karstensrage> so i dont get how it works on 14.04 if everything was compiled with 12.04's libs?
[16:39] <Rhonda> And depending on whether they have some abi/api incompatible changes or not you would need to recompile it on 14.04 … or not. :)
[16:39] <Rhonda> Libraries have a thing called ABI and API, which stands for Application Binary/Programming Interface.
[16:40] <Rhonda> And if that is compatible (like, only gets extended, not structure changed, things dropped or similar), even when compiled against the old versions it still will work with the newer ones.
[16:41] <Rhonda> Otherwise you would need to recompile every single package after an upgrade of one library, which would be highly inconvenient. :)
[16:41] <Rhonda> Some libraries are known to regularly break and fumble with those interfaces, but most are quite conservative with changes in that area.
[16:42] <karstensrage> so maybe i should not worry about that issue and just hope for the best?
[16:42] <Rhonda> Yes.
[16:42] <karstensrage> hmm ok
[16:42] <karstensrage> is that link i posted the best place to get started?
[16:44] <Rhonda> Take a look at the francine package.  I last uploaded it to Debian in 2005.  Which was during the etch (4.0) release cycle.
[16:44] <Rhonda> We are now at Debian 8, there was no need to recompile it once since, the same binary from 10 years ago still runs on current Debian.
[16:45] <Rhonda> That I don't know, I haven't read it, but it might be useful. :)
[16:46] <Rhonda> Especially with respect to packaging libraries there is a bit more needed from what I know, but I never packaged a library myself, so can't help you there.
[16:46]  * Rhonda . o O ( speaking of francine, working on finally updating the package to current best practices, and getting rid of my old name) )
[16:46] <karstensrage> ok, thank you, that helps so far, does ubuntu have mentors that help with things?
[16:47] <karstensrage> and i have to get somethign like a sponsor to actually get it into the packaging system?
[21:29] <karstensrage> im getting this error and nothing is coming up on google
[21:30] <karstensrage> dh_install: mylib-dev missing files (usr/include/*), aborting
[21:31] <karstensrage> Rhonda, the path im taking is building two packages, one for the library and one for the pam module that depends on the library, thats correct right?
[21:33] <Rhonda> Guess so, and the library needs the files in the -dev package required to build stuff against it, which means the include files.
[21:34] <karstensrage> ok how do i do that?
[21:35] <Rhonda> Can't mentor your with library packaging, but doesn't the library contain include files?
[21:35] <karstensrage> yes
[21:35] <karstensrage> yes it does
[21:37] <karstensrage> how do i find someone that can mentor for libraries?
[21:37] <karstensrage> i feel bad asking tbh
[21:38] <karstensrage> but its really not a familiar thing to me