Re: [ELPA] New package: breadcrumb.el

[João Távora]

On Tue, Sep 5, 2023 at 7:21 AM Philip Kaludercic <philipk@posteo.net> wrote:

> >> If possible, it would be nice to track this on your end with a
> >> .elpaignore file.
> >
> > That's perfectlky doable, but I do think it makes a bit more sense like
> > this.  Why do you think it's "nicer"?  And can we merge it as is for now
> > (so I can tick this off my todo? ;-)
>
> The advantage of having this information locally in your repository is
> that if anything changes (files are added or renamed), it is easier to
> update what files shouldn't be bundled in the release tarball, instead
> of having to change stuff in elpa.git.  I guess in your case it doesn't
> matter that much because you also have push-access to the repository.
> "Nice" just means that we avoid small "Add foo.bar to :ignored-files for
> baz" commits, that are more noisy than useful.

I guess so, but there's also the case to be made that we want to keep
repos package-repository-agnostic.  breadcrumb.el is really intended to go
into GNU ELPA .  But maybe straight.el has a .straightignore and so on...
And el-get (if it is still alive) has something else, etc.
IMO it's a good principle to have meta info nearest to where it's
actually used, and in this case it would be elpa.git.  But as I said,
I don't mind adding it, so if you want open a PR over at the breadcrumb
upstream and I'll merge it.

Anyway, if there are no objections, and you don't beat me to it, I'll
push the (revised) patch to elpa.git later today.

João