Re: [libgpiod][PATCH] README: add info about the github page

[Kent Gibson <warthog618@gmail.com>]

On Fri, Jan 12, 2024 at 05:07:42PM +0100, Bartosz Golaszewski wrote:
> On Fri, Jan 12, 2024 at 4:40 PM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > On Fri, Jan 12, 2024 at 11:25:02PM +0800, Kent Gibson wrote:
> > > On Fri, Jan 12, 2024 at 04:05:46PM +0100, Bartosz Golaszewski wrote:
> > > > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > > >
> > > > The github page over at https://github.com/brgl/libgpiod has been reopened
> > > > for bug reports and discussions. Add a link and a mention to the README
> > > > file.
> > > >
> > >
> > > No problem with the patch, but the github page itself seems to have
> > > Issues and Discussions disabled.  And the Wiki might be useful too?
> > >
> >
> > The Releases section could use updating - it lists the latest as v0.3
> > from June 2017!
> >
>
> I don't want to do releases on github. The right place to fetch the
> releases from is kernel.org[1] (I should add this link to README too)
> and I don't want to duplicate release tarballs. I'm pretty sure people
> would start fetching releases from github for distros etc.
>

Uugh, yeah github automatically provides tarballs for releases and there
is no way to disable that. I was thinking you could just use it to advertise
a particular tag as a release, but don't want the additional tarballs
floating around.  So, yeah, definitely need to add links to the official
sources for tarballs, cos they can still download a zip of the tree, even
if you haven't provided the tags.

And, if you have time, adding an issue describing the daemon and where
you are at would be really helpful.  Though that is currently living in
the topic/dbus branch of libgpiod-private, right?

Cheers,
Kent.