git-cmd.)
@mingwandroid, WRT :point_up: January 10, 2021 11:27 PM no worries, I'm not in a rush to have it done, just slightly annoyed/frustrated because finding the workaround is being harder than packaging several other tools. Hope they let you out soon! (despite not having much outside to go to :S)
Thanks @umarcor , I am back now. I must say that the Spanish health service took good care of me, despite my sorely lacking Spanish language skills. I will not say too much about the food, because as my dear Mum often says "if you can't say something nice it's best to say nothing at all" ;-)
Random thought. Is it possible to create a bot in github which will comment when a issue is fixed and the package is uploaded?
@Biswa96, it's pretty trivial to comment/open/close issues in GitHub using any library for interacting with the API, such as octokit (js) or pyGitHub (Python). However, I did not understand where do you want the comment to be posted. Can you please clarify?
@mingwandroid thanks so much. I'm glad you liked it. In fact, I tried not to duplicate the content of msys2's docs, so that my "workflow guidelines" can be potentially moved there in the future. Yet, I'm still shaping and reworking my own workflow, so it's pretty organic work in progress for now. E.g. it was initially a fork of MINGW-packages, but then lazka could not edit the PRs because he was not a member of that org, so I had to fall back to using my personal fork for PRs. Overall, I think it can be interesting to create documentation for "packager camps" in the MSYS2 ecosystem, which can offload the main maintainers from niche issues related to multiple packages in some area. This is already done in larger teams, such as Debian or Fedora. In both cases, there is an EDA related group of tools and people.
Noticed a broken link though: https://github.com/hdl/smoke-tests/blob/main/CONTEXT.md
Thanks for pointing that out! 'HDL' is undergoing some fast and disruptive changes, because we are aiming at bringing together packagers from different EDA tooling camps. https://github.com/hdl/packages was a created a couple of days ago, and the context is now located there. I will fix the broken link.
BTW, you might find all the litex-conda-* packages interesting/exciting or maybe infuriating ( :laughing: ), due to your background. Those are soon to be transferred from litex-hub to hdl.
@mingwandroid, personally, I would be happy to hear your thoughts about this parallel/concurrent packaging approach:
- MINGW-packages (+ pip with a little mouth :blush: ).
- Conda.
- Containers (Docker/Podman).
My hope is that different people can take care of each of those approaches, but handle it so that users can pick any of them as their "system/tooling management solution". That is, "project management scripts for hdl designs" should be able to use tools installed using any of those methods/ecosystems.
@mingwandroid
There's the R world and Julia also to consider!
Yes. However, the language of choice in EDA is Python (probably for the following couple of decades at least). It was TCL for 2-3 decades, and many vendor tools do still only support TCL for scripting. Hence, there is a long way yet until "too modern" environments such as R or Julia meet EDA.
We have MSYS2 packages in conda to help with building stuff mostly, and also for R but it is out of date.
Conda-forge would probably love someone to update MSYS2-in-conda and automate the continual update of the same, too.
I lost the scripts I wrote in 2016 that I used to do the original import. I added libalpm packages to conda as I remember and parsed the MSYS2 metadata. Now-a-days, I'd rather conda-forge built MSYS2 packages from source using the PKGBUILDs.
I'm not following you completely, but it sounds quite exciting. Did I understand correctly and you are suggesting it's possible to use MSYS2 packages (or recipes), and have them wrapped in Conda? Is that for Windows targets only, or would the same apply for Linux targets (using Arch's recipes)?
I worked with Tim Ansell before actually. He helped us to get our linux-64 compilers in shape in a few ways.
The litex-conda stuff is actually being done by people from Antmicro, who are working with mithro in SymbiFlow. In fact, those litex-conda packages were located in SymbiFlow and Antmicro orgs, they were merged into litex-hub and now are to be moved into hdl.
Actually Anaconda Inc. are looking for people to work on this kind of thing if anyone was interested in doing it professionally.
Conda-forge would probably love someone to update MSYS2-in-conda and automate the continual update of the same, too.
Just to clarify, do you mean someone working on allowing any user to have Windows targets in Conda "for free" as long as the project/tools exists on MSYS2 repos?