RE: About the opam package
Hi, Brian! Thank you for your detailed explanation! I only sent a pull request to Andy's repository this time, but if I need to do the other work, I will definitely refer to my notes based on what you taught me! Thanks, Sora From: Brian Inglis Sent: Wednesday, July 15, 2020 10:43 AM To: cygwin-apps@cygwin.com Cc: Sora Morimoto Subject: Re: About the opam package On 2020-07-14 17:17, Sora Morimoto wrote: > Hi everyone. I am a developer involved in the development of the OCaml > ecosystem. > First of all, I am not yet used to using a mailing list as a method of > communication. I believe I have done enough research before coming here, but I > apologize in advance if I make any mistakes. > Now, I wanted to help with the maintenance of the opam package for Cygwin, > but after reading the documentation I still do not know what to do. > Specifically, I do not even know where the build script source is, and where > to send the patch. > Can someone please teach me? Using the Cygwin Setup program, install: * cygport package - standard method for building and maintaining packages for the Cygwin distribution - similar to Gentoo Portage but not compatible with it - Setup will auto-install all required build tools which are its dependencies * any ocaml-... packages you need * Opam * possibly Opam-installer and check the Install sources checkbox on that/those latter. The sources are normally installed under /usr/src/ IIRC. To rebuild a package build using cygport, cd into the /usr/src/$PKG (replace by actual package name - use tab completion if your shell supports that) directory, check the $PKG.cygport file to see if there are any extra build dependencies you need to install before proceeding (REQUIRES are *runtime* dependencies auto-installed by Setup when a package is installed). To rebuild a cygport package (to check your setup includes all the tools and libraries needed before making any changes) just run: $ cygport $PKG.cygport download all test which will download the upstream sources, build and create an installable Cygwin package, and run any tests included in the package. For more information about cygport run: $ cygstart /usr/share/doc/cygport/html/manual/index.html to open the manual in your default browser, or check out ocaml related entries: $ cygstart /usr/share/doc/cygport/html/manual/masterindex.html#O -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]
RE: About the opam package
Hi, Andy! I know you well and was surprised to know that you are the maintainer of this package. I just sent a PR to your repository. Thank you, Sora From: Andy Li Sent: Wednesday, July 15, 2020 11:25 AM To: Sora Morimoto Cc: cygwin-apps@cygwin.com Subject: Re: About the opam package Hi, On Wed, Jul 15, 2020 at 7:17 AM Sora Morimoto wrote: > Now, I wanted to help with the maintenance of the opam package for Cygwin, > but after reading the documentation I still do not know what to do. > Specifically, I do not even know where the build script source is, and where > to send the patch. I'm the maintainer of the opam cygwin package. (FYI, you can see the list of cygwin package maintainer at https://cygwin.com/cygwin-pkg-maint) The package source is at https://github.com/andyli/opam-cygwin Feel free to send me PR. Best, Andy
Re: About the opam package
Hi, On Wed, Jul 15, 2020 at 7:17 AM Sora Morimoto wrote: > Now, I wanted to help with the maintenance of the opam package for Cygwin, > but after reading the documentation I still do not know what to do. > Specifically, I do not even know where the build script source is, and where > to send the patch. I'm the maintainer of the opam cygwin package. (FYI, you can see the list of cygwin package maintainer at https://cygwin.com/cygwin-pkg-maint) The package source is at https://github.com/andyli/opam-cygwin Feel free to send me PR. Best, Andy
Re: About the opam package
On 2020-07-14 17:17, Sora Morimoto wrote: > Hi everyone. I am a developer involved in the development of the OCaml > ecosystem. > First of all, I am not yet used to using a mailing list as a method of > communication. I believe I have done enough research before coming here, but I > apologize in advance if I make any mistakes. > Now, I wanted to help with the maintenance of the opam package for Cygwin, > but after reading the documentation I still do not know what to do. > Specifically, I do not even know where the build script source is, and where > to send the patch. > Can someone please teach me? Using the Cygwin Setup program, install: * cygport package - standard method for building and maintaining packages for the Cygwin distribution - similar to Gentoo Portage but not compatible with it - Setup will auto-install all required build tools which are its dependencies * any ocaml-... packages you need * Opam * possibly Opam-installer and check the Install sources checkbox on that/those latter. The sources are normally installed under /usr/src/ IIRC. To rebuild a package build using cygport, cd into the /usr/src/$PKG (replace by actual package name - use tab completion if your shell supports that) directory, check the $PKG.cygport file to see if there are any extra build dependencies you need to install before proceeding (REQUIRES are *runtime* dependencies auto-installed by Setup when a package is installed). To rebuild a cygport package (to check your setup includes all the tools and libraries needed before making any changes) just run: $ cygport $PKG.cygport download all test which will download the upstream sources, build and create an installable Cygwin package, and run any tests included in the package. For more information about cygport run: $ cygstart /usr/share/doc/cygport/html/manual/index.html to open the manual in your default browser, or check out ocaml related entries: $ cygstart /usr/share/doc/cygport/html/manual/masterindex.html#O -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]
About the opam package
Hi everyone. I am a developer involved in the development of the OCaml ecosystem. First of all, I am not yet used to using a mailing list as a method of communication. I believe I have done enough research before coming here, but I apologize in advance if I make any mistakes. Now, I wanted to help with the maintenance of the opam package for Cygwin, but after reading the documentation I still do not know what to do. Specifically, I do not even know where the build script source is, and where to send the patch. Can someone please teach me?
Re: [ITP] xxhash 0.7.4-1
> On 14 Jul 2020, at 21:51, Doug Henderson via Cygwin-apps > wrote: > > On Tue, 14 Jul 2020 at 10:29, ASSI <> wrote: >> >> ASSI writes: >>> By patching the Makefile, just like you need to do for all the other >>> stuff from the same author. You can have a look at the zstd packages. >> >> Come to think of it, xxhash is already part of zstd. Can't you just >> link to that? >> >> >> Regards, >> Achim. > > I have patched the Makefile as suggested. The newest version of the > dist files as located at > > https://github.com/djhenderson/Temp/raw/master/xxhash.zip > > (...) > > Any way, I would like some critical feedback on the dist packaging. Many thanks Doug, really nice work ! At least I successfully manage to build rsync with this package : $ uname -s -r CYGWIN_NT-6.1 3.1.6(0.340/5/3) $ ./rsync --version rsync version 3.2.3dev protocol version 31 (...) Optimizations: no SIMD, asm, openssl-crypto Checksum list: xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none Not sure about the other things to check though. Kind regards, Ben
Re: [ITP] xxhash 0.7.4-1
On Tue, 14 Jul 2020 at 10:29, ASSI <> wrote: > > ASSI writes: > > By patching the Makefile, just like you need to do for all the other > > stuff from the same author. You can have a look at the zstd packages. > > Come to think of it, xxhash is already part of zstd. Can't you just > link to that? > > > Regards, > Achim. I have patched the Makefile as suggested. The newest version of the dist files as located at https://github.com/djhenderson/Temp/raw/master/xxhash.zip I compared the xxhash sources between the xxhash repo and the zstd repo. There are major differences in the code. This is obvious from wc $ wc -l /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.c /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.c 43 /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.c 864 /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.c 907 total $ wc -l /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.h /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.h 2076 /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.h 285 /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.h 2361 total I had a brief look at the code, but did not attempt to judge the merits of either code base. The zstd repo does not include the xxhsum command which has a similar CLI to cksum, md5sum, sha256sum, etc. Apparently xxhash will use the SSE2 instructions for some operations. Someone with an older CPU without those instructions should test to make sure the xxhsum programs works for them. (I'm just saying that, I don't really know what that means.) Any way, I would like some critical feedback on the dist packaging. Thanks, Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com
Re: Attention ninja maintainer
Re: Attention ninja Yes! The shinobi answer your call, leaving their hidden villages, ready to spread fire and confusion amongst our enemies, under cover of darkness! Re: Attention ninja maintainer Oh, how disappointing :( On 13/07/2020 18:46, Doug Henderson via Cygwin-apps wrote: Hi, ninja installs its bash completion script in /etc/bash-completion.d Other bash completions are installed to /etc/bash_completion.d Please look into this. Yeah, this is a packaging error due to a typo in the cygport for ninja. Should be fixed as of ninja 1.10.0-2. Thanks for reporting this.
Re: [ITP] xxhash 0.7.4-1
ASSI writes: > By patching the Makefile, just like you need to do for all the other > stuff from the same author. You can have a look at the zstd packages. Come to think of it, xxhash is already part of zstd. Can't you just link to that? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [ITA] python-imaging
On 10/07/2020 13:24, marco atzeri via Cygwin-apps wrote:
> On Fri, Jul 10, 2020 at 12:28 PM Hamish McIntyre-Bhatty via Cygwin-apps
> wrote:
>> On 10/07/2020 01:20, airplanemath via Cygwin-apps wrote:
I tend to use loops like
for ver in ${PYTHON_WHEEL_VERSIONS//:/ };
do
/usr/bin/python${ver} script
done
for the tests. Also, I believe ${ARCH} is the same as $(uname -m) here,
if you want to streamline the PYTHONPATH definition a bit. Both of
those are personal style and you are entirely welcome to ignore this.
This worked a treat.
Other than that, I noticed you're writing your own src_compile and
src_install. Is there some reason python_wheel_compile and
python_wheel_install aren't working for you? I haven't noticed a problem
with either of those functions in the past year or so. (For reference, the
value of PYTHON_WHEEL_VERSIONS determines which python versions
are compiled: see
https://cygwin.github.io/cygport/python-wheel_cygclass.html#robo361).
This also worked really well, thanks for the tip :)
> I am not bothering with 3.5 for my builds.
> The focus should be to have 3.8 up and running
> so 3.6:3.7:3.8 are enough
Okay. I've updated my test packages, and they are available at
https://www.hamishmb.com/files/cygwin-temp/ as before. Please let me
know if I'm now good to go or if there are any more issues.
Hamish
0x87B761FE07F548D6.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
