[DO NOT MERGE!] Proposed packaging for opam releases

[dra27]

On my fork I have two branches 20240902-1 and opam which demonstrate a proposed means of producing tarballs automatically from GitHub commits.

This PR isn't intended to be merged; assuming we're happy with this I will push these two branches to this repo.

The idea is to create a package which when installed in opam provides the files needed for winpthreads when configuring OCaml (the packaging for Windows handles flexdll in the same way).

The tarball produced by this branch contains:

C:\Devel>tar tf 20240902-1.tar.gz
winpthreads-20240902-1/
winpthreads-20240902-1/COPYING
winpthreads-20240902-1/README
winpthreads-20240902-1/include/
winpthreads-20240902-1/include/pthread.h
winpthreads-20240902-1/include/pthread_compat.h
winpthreads-20240902-1/include/pthread_signal.h
winpthreads-20240902-1/include/pthread_time.h
winpthreads-20240902-1/include/pthread_unistd.h
winpthreads-20240902-1/include/sched.h
winpthreads-20240902-1/include/semaphore.h
winpthreads-20240902-1/src/
winpthreads-20240902-1/src/barrier.c
winpthreads-20240902-1/src/barrier.h
winpthreads-20240902-1/src/clock.c
winpthreads-20240902-1/src/cond.c
winpthreads-20240902-1/src/cond.h
winpthreads-20240902-1/src/libgcc/
winpthreads-20240902-1/src/misc.c
winpthreads-20240902-1/src/misc.h
winpthreads-20240902-1/src/mutex.c
winpthreads-20240902-1/src/nanosleep.c
winpthreads-20240902-1/src/ref.c
winpthreads-20240902-1/src/ref.h
winpthreads-20240902-1/src/rwlock.c
winpthreads-20240902-1/src/rwlock.h
winpthreads-20240902-1/src/sched.c
winpthreads-20240902-1/src/sem.c
winpthreads-20240902-1/src/sem.h
winpthreads-20240902-1/src/spinlock.c
winpthreads-20240902-1/src/thread.c
winpthreads-20240902-1/src/thread.h
winpthreads-20240902-1/src/winpthread_internal.h
winpthreads-20240902-1/src/wpth_ver.h
winpthreads-20240902-1/winpthreads.install

[shym]

This is a very elegant solution to package winpthreads, congratulations!
I pushed a couple of small suggestions with 2 commits on my 20240902-1 branch.
And I wondered about your first commit as I see it empty: was that on purpose?

[shym]

Typo: this a comment instead of a shebang :-)

[dra27]

Whoops!!

[dra27]

Obviously, I meant it to be a Sixth Edition Unix Shell Script 😉

[shym]

Wasn’t that meant to be 20240209 rather than 20240902?

[dra27]

Thanks, @shym - I've force pushed both typo suggestions to https://github.com/dra27/winpthreads/commits/opam.

For the shell script, I guess I spend too long contorting around sh scripts, because one can't guarantee the presence of bash, but that really doesn't matter here! I had one question, though - is there a technical reason to prefer printf vs echo? In this case, echo seems clearer, but I wonder that I'm missing something?

[dra27]

Branches pushed!

[shym]

is there a technical reason to prefer printf vs echo?

I just found printf ' "%s" { "%s" }\n' "$f" "$f" easier to read than echo " \"$f\" { \"$f\" }" and then used printf everywhere for uniformity.
(I often end up replacing echo because echo -e is not portable, but that isn't a concern here)