Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Include headers and static libs in packages and add a way for dbc to expose them programmatically

Abierto
#96 3 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
go
Área
cli

Línea de trabajo

Start by reading the dbc CLI entry points and the code that installs and packages ADBC drivers; the issue does not identify specific files or tests. Determine how driver packages can include headers and static libraries, and how a dbc info --pkg-config DRIVER command would expose their include and library flags. Done means packages contain those development files and the command prints the corresponding flags; the issue has had no recent comment for over a year.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

idea

dbc installs drivers as shared libraries on the user's system so they can load those drivers with a driver manager of their choosing. Inspired by the pain that projects like duckdb-rs go through with a library like libduckdb, dbc could help software packagers too, not just analysts.

What if dbc could behave kind of like a pkg-config? While it'd be better for everyone if every ADBC driver had a devel package on every packaging system, this is unlikely to ever happen. So dbc could have something like a dbc info --pkg-config DRIVER subcommand that would print out -I and -L flags. This would require driver packages to include those files of course.

Lenguaje dominante
Go
Estrellas
154
Forks
15
Merge medio
1 d 2 h
PR fusionados (30 d)
15

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de columnar-tech/dbc

Todos los issues de columnar-tech/dbc

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.