[09:03] good morning all [09:03] anyone in here? [09:20] ok then [09:20] bunch of tards === asac_ is now known as asac === matt_c_ is now known as matt_c [16:37] in a debian package can I list dependencies as libraries as opposed to package names, and have the libraries resolved by the pkg manager ? [16:38] i'm working on packaging apps for the intel app store. One goal is to be able to create a single DEB package that would install on multiple Moblin-compliant DEB distributions, yours being one. [16:38] but ubuntu package names sometimes differ from other DEB distros, so I'd like to list the dependencies in the packages as libraries [18:10] bspencer: Usually, you install ELF binaries in your packages and they have ELF dependencies on the ELF libraries you need; dh_shlibdeps then generates deps on real packages from these [18:12] lool: hello my friend [18:12] hope all is well [18:12] All is well; how about you? [18:13] thx good. [18:14] If I create a control file, I can or can't put libraries in the "Depends" field? [18:14] how do I specify my dependencies? [18:15] You should put ${shlibs:Depends} in Depends: [18:15] And dh_shlibdeps will do the right thing [18:18] so I could put: [18:18] Depends: ${shlibs:libarchive.so.1} libwww-perl, acme-base (>= 1.2) ${shlibs:libapr-1.so.0} [18:19] where libwww-perl is the pkg, but libarchive.so.1 is the library (just pulling random) [18:20] bspencer: No, it's literally "${shlibs:Depends}" [18:20] ah, and then it scans my app and determines the dependencies for me [18:20] bspencer: dh_shlibdeps will generate "shlibs:Depends" from the installed libs and the ELF deps [18:20] Yes [18:20] snazzy [18:21] and it will pull in the packages and prompt the user [18:21] at install time [18:21] ok. I'll play with that [18:23] is shlibs a Canonical-specific tool? [18:23] or Debian standard [18:24] Prompt the user? [18:24] bspencer: This is Debian policy stuff [18:24] bspencer: You might want to look at existing packages perhaps? [18:25] thx