Re: url2pkg and pypi

[Roland Illig <roland.illig%gmx.de@localhost>]

Am 31.12.2021 um 13:36 schrieb Greg Troxel:
> Benny Siegert <bsiegert%gmail.com@localhost> writes:
>
> > On Fri, Dec 31, 2021 at 2:03 AM Greg Troxel <gdt%lexort.com@localhost> wrote:
> > > So this is likely my error, but I had no idea that after I edited and
> > > exited the file would change.   Seems better to do that before if that's
> > > feasible.
> >
> > That's unfortunately not feasible AFAIU. url2pkg only fetches the
> > distfile after you exit the editor for the first time. After fetching
> > and extracting, it gathers more information and updates the Makefile.
>
> man page says:
>
>       url2pkg takes the URL to a package's distfile that should be turned into
>       a package.  It fetches the distfile, extracts it, and by looking at the
>       extracted files, fills in some variables in the package Makefile.
>
> which is different from what you just said.
>
> If there's truly a "you edit some and save and then it changes it more"
> it would be nice to explain that.

Instead of syncing the man page to reality, I'd rather remove all
interactivity from url2pkg.  In the cases I experienced, it was not
necessary to edit the package Makefile before downloading the distfile.

I don't remember why I wrote that "in almost all cases the package needs
manual work" two years ago, I don't have any evidence for that claim.

Does anyone have different experiences and can share example URLs that
need adjustments _before_ downloading the distfile?

Roland