[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Go (golang) packaging, part 2

Hi Chow,

Chow Loong Jin <hyperair@debian.org> writes:
>  1. If software that depends on native packages is installed using "go get"
>     or whatever other language-specific package manager, e.g. pip for Python or
>     gem for Ruby is installed, there is no way to declare a dependency on
>     those. For example, the Python mysql bindings require some MySQL C headers
>     which are available in Apt, but you won't know until your pip install run
>     fails due to missing headers. After you're done, you move on to your next
>     dependency which also fails due to missing headers, and the next, and the
>     next…

>  2. If something installed from your language-specific package manager is in a
>     path that a Debian package overrides, dpkg is going to barf because it
>     doesn't know where those files come from. This of course applies to
>     randomly ./configure-ing stuff with --prefix=/usr and running make
>     install.
Not going to happen in case of go. “go get” _always_ installes into a
user-defined path with ~/gocode being the recommendation.

>  3. Software packages from Apt cannot declare dependencies against
>     language-specific packages, for the same reasons highlighted in
>     #1.
Irrelevant argument in our case, as outlined earlier in the discussion.

Best regards,

Reply to: