[aur-general] Go package dependencies

Adam Levy theadamlevy+archlinux at gmail.com
Wed Feb 28 01:48:45 UTC 2018


Good to know. I will update my PKGBUILDs accordingly.

Thank you

On Tue, Feb 27, 2018 at 4:33 PM, Levente Polyak via aur-general <
aur-general at archlinux.org> wrote:

> On 02/28/2018 02:23 AM, Adam Levy via aur-general wrote:
> > Hi there,
> >
> > I am co-maintaining a few AUR packages written in Golang and I just ran
> > namcap on my built package. I got the following output on a few of my
> > golang packages:
> >
> > $ namcap influxdb-1.4.3-1-x86_64.pkg.tar.xz
> > influxdb E: Dependency glibc detected and not included (libraries
> > ['usr/lib/libpthread.so.0', 'usr/lib/libc.so.6'] needed in files
> > ['usr/bin/influx_inspect', 'usr/bin/influx_stress', 'usr/bin/influx',
> > 'usr/bin/influx_tsm', 'usr/bin/influxd'])
> >
> > However 'glibc' is in the base group, and I thought that it wasn't
> > necessary to declare dependencies from the base group since it should
> > always be installed on a fresh OS install. Am I wrong about this point?
> > Should I be including 'glibc' as a dependency in this package? Should I
> be
> > including 'bash' as a dependency in packages with scripts that use bash?
> >
> > Thank you!
> > Adam Levy (alaskanarcher)
> >
>
> Actually there is no strict rule that base must be installed, its just a
> strong recommendation. While most systems would be quite useless without
> having glibc, its still a first level dependencies that a package uses
> and therefor should be declared explicitly and not implicitly.
> Opinions vary, but if you ask me its cleaner to explicitly state first
> level dependencies, no matter from where they may be implicitly
> available (so yes, personally i add both, glibc and bash if required).
>
> cheers,
> Levente
>
>


More information about the aur-general mailing list