waddlesplash

You can clone the repository by creating a case-sensitive filesystem image, the same as for building Haiku. Here's an old guide that details how to do it: https://www.haiku-os.org/articles/2015-02-05_building_haiku_mac_os_x_1010_yosemite/#disk_image

The reversion was done by @korli. > to just install the HaikuPorter package in the system with pip command But HaikuPorter does have real usages outside of Haiku, namely bootstrap...

> There are many use cases and reasons to make possible for the people to normally (without any issues) clone repository. Like what? > This should be possible to be...

> This should cost about zero effort. Except there are usages of `haikuporter` directly from this repository in other repositories, including HaikuPorts itself, the Haiku build system, the buildmaster Docker...

> Next option would be setting core.ignoreCase in git config to false but it's not working. This works with a case-sensitive disk image. Did you follow the instructions here? https://www.haiku-os.org/articles/2015-02-05_building_haiku_mac_os_x_1010_yosemite/#disk_image...

The "build_packages" system needs to make new repo files from scratch for a variety of reasons, so having a way to pass in .PackageInfos with SHA256 already computed to `package_repo`...

I think we should just move forward with the refactor of HaikuPorter to split the "Buildmaster" logic out into a separate project, and to just have HaikuPorter itself operate in...

Well, part of the work I was going to do with the refactor I mentioned above in splitting out the "Buildmaster" logic would be to make the frontend and its...

But what changes does this actually produce, then? Most of the differences are due to those 3 problems I noted. Once they are corrected, what "differences" will remain? I think...

I don't know if we can use machine-formatted code, due to the second item listed above at least (comments on next lines should be indented.) There's probably others (e.g. I...