Re: [PATCH] Install new autoreconf files.

Am 14.04.26 um 00:34 schrieb Steffen Nurpmeso:
> Oswald Buddenhagen via Mutt-dev wrote in
>   <[email protected]>:
>   |On Mon, Apr 13, 2026 at 06:21:22PM +0800, Kevin J. McCarthy wrote:
>   |>https://www.gnu.org/software/gettext/manual/html_node/Distributed-Develo\
>   |>pment.html
>   |>
>   |>However, if it I did something wrong, then let's talk about what needs
>   |>to be changed.
>   |>
>   |it's not wrong per se. it's more of a philosophy thing, whether you want
>   |to do pure source control, or want to veer toward configuration
>   |management. at the extreme end, you would be committing binaries for
>   |every supported platform for each release. i'm a source control purist,
>   |and would therefore delete (and gitignore) every file that is somehow
>   |generated by/from something else in the repo.
>
> It has come to that.  But traditionally -- as i perceive(d) it --
> projects were buildable and installable out of the box.
> They also had readily usable Unix manual pages, regardless of how
> these were managed on the source level.
[...long rant snipped...]
> In short.  I personally *love* to simply check something out, and
> be able to build and install, and that includes manual pages.
> I (still personally) can absolutely understand the desire to have
> easy usable abstractions when developing, but including a readily
> prepared set, at least at times, or on a dedicated branch, even if
> that is rebased / re-build-up frequently, or whatever, you know?


You missed the one valid point about "many" dependencies, and that's 
that they also present many attack vectors along the supply chain.


The other aspect is that there is a difference between releases and 
intermediate states in development - from a user perspective I would 
expect documentation inside the *release* tarball that has the sources, 
and .md or .rst or .txt are nice, .html I can live with, if I get 
redirected to a web site, that's disaster waiting to happen.
   I don't expect as much convenience from interim versions during 
development; and CI/CD allows to build a full-fledged snapshot tarball 
that has the same artifacts built as your regular release but just 
having the CI/CD do a "make distcheck" or "make dist" and uploading that 
if you want, and if you assume people will actually use those.

For "I want to check this out", getting the stuff installed once, 
possibly with a script into a container image that you commit to an 
image on disk when the container stops running so that you can restart 
it later is a possibility.