[Pkg-javascript-devel] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Jérémy, So you don't want to provide the virtual package because packages which depend on it will likely break? I know in at least one case the portion of the API that my package used worked with multiple versions of libv8 but the package naming issue forced my users to install libv8 manually. Actually, what I really need to do is get my source package into the Debian system. I have a fairly popular and mature Open-Source project but I've been overwhelmed by the Debian package submission process and still don't fully grock it. Joseph On Sat, November 22, 2014 2:59 pm, Jérémy Lal wrote: > Le samedi 22 novembre 2014 à 13:26 -0800, Joseph Coffland a écrit : >> ../.. The problem >> stems from the fact that libv8 includes the library version in the >> library >> name not just in the package name. I know this has become common (boost >> does too) but it's a PITA for packages which depend on such packages. > > Actually there's a reasonable explanation for that fact : > upstream libv8 doesn't care about API compatibility between versions, > even patch-level updates can break API. > Even when API compatibility matches their version numbers, ABI > compatibility is not something upstream tries to ensure. Note that it is > more difficult to achieve with C++ libs than with C libs. > Like Boost indeed, programs depending on a given version will often > require patches to be able to be built on a later minor update, and must > all be rebuilt in any case (because of potential ABI incompatibilities). > This is a PITA - not only for debian - for all other programs depending > on libv8 and that mostly explain also why nodejs 0.10 branch was stuck > with libv8-3.14. > > I hope that (kind of) rant gives you a clearer view of the situation. > > Jérémy. > > > > -- Cauldron Development LLC http://www.cauldrondevelopment.com/ Cell: 208-409-9128 ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Le samedi 22 novembre 2014 à 13:26 -0800, Joseph Coffland a écrit : > ../.. The problem > stems from the fact that libv8 includes the library version in the library > name not just in the package name. I know this has become common (boost > does too) but it's a PITA for packages which depend on such packages. Actually there's a reasonable explanation for that fact : upstream libv8 doesn't care about API compatibility between versions, even patch-level updates can break API. Even when API compatibility matches their version numbers, ABI compatibility is not something upstream tries to ensure. Note that it is more difficult to achieve with C++ libs than with C libs. Like Boost indeed, programs depending on a given version will often require patches to be able to be built on a later minor update, and must all be rebuilt in any case (because of potential ABI incompatibilities). This is a PITA - not only for debian - for all other programs depending on libv8 and that mostly explain also why nodejs 0.10 branch was stuck with libv8-3.14. I hope that (kind of) rant gives you a clearer view of the situation. Jérémy. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Jérémy, > Your package won't install on some systems anyway, since libv8 does not > build/run on all architectures. I don't need it to install on all systems. Just the ones I support which are the same as for libv8. >>From what you say it looks like your package dependency on libv8 is > optional ? If that's the case then use a Recommends or Suggests > relationship in debian/control. I don't think I explained my problem or the solution well enough. What I would like to have is a virtual package named 'libv8' which depends on the latest 'libv8-#.#.#', whatever that maybe. This way my package only needs to depend on 'libv8' and not have to guess the version that might be installed on the user's system. Also you could then install libv8 like this: sudo apt-get install libv8 Right now you have to first search for the latest version. The problem stems from the fact that libv8 includes the library version in the library name not just in the package name. I know this has become common (boost does too) but it's a PITA for packages which depend on such packages. Thanks, Joseph -- Cauldron Development LLC http://www.cauldrondevelopment.com/ Cell: 208-409-9128 ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Le jeudi 20 novembre 2014 à 17:45 -0800, Joseph Coffland a écrit : > Package: libv8-3.14.5 > Version: 3.14.5.8-8 > Severity: normal > > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages libv8-3.14.5 depends on: > ii libc6 2.19-10 > ii libgcc1 1:4.9.1-12 > ii libstdc++6 4.9.1-12 > > libv8-3.14.5 recommends no packages. > > libv8-3.14.5 suggests no packages. > > -- no debconf information > > > Adding a virtual package named libv8 will make it much easier to create > packages which depend on libv8. > > I'm having a problem with a binary package I've created which depends on > libv8. If I specify a dependency on > libv8-3.14.5 directly then my package wont install on some systems. If I > leave out the dep then my software > wont run with out the user manually searching for the latest version of libv8 > and installing it. > > Please help. Your package won't install on some systems anyway, since libv8 does not build/run on all architectures. >From what you say it looks like your package dependency on libv8 is optional ? If that's the case then use a Recommends or Suggests relationship in debian/control. Jérémy. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Package: libv8-3.14.5 Version: 3.14.5.8-8 Severity: normal -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libv8-3.14.5 depends on: ii libc6 2.19-10 ii libgcc1 1:4.9.1-12 ii libstdc++6 4.9.1-12 libv8-3.14.5 recommends no packages. libv8-3.14.5 suggests no packages. -- no debconf information Adding a virtual package named libv8 will make it much easier to create packages which depend on libv8. I'm having a problem with a binary package I've created which depends on libv8. If I specify a dependency on libv8-3.14.5 directly then my package wont install on some systems. If I leave out the dep then my software wont run with out the user manually searching for the latest version of libv8 and installing it. Please help. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
