Adoption

[fzerorubigd]

All major distros that have jcal, are using the original repository. The goal is to switch them to use this repository instead, but on the other hand it is understandable that this fork (due to the situation) has no ties (other than being a fork) with the original repository.
I tried to fix the homebrew and the change was rejected (again: understandable and to be honest I like brew now because of that and think of using it)
But if someone can do something about it, please help.

[niyumard]

Currently there are two versions of proxychains in Debian's distro. proxychains and proxychains4 (which is proxychains-ng). But the new version has the binary for proxychains and the other one can be called via proxychains3. Maybe we should try taking the -ng approach?

---

در حال حاضر دو نسخه از proxychains توی توزیع دبیان هست: proxychains و proxychains4 (که همون proxychains-ngه). اما نسخه جدید باینری proxychains رو در دست داره. نسخه‌ی قدیمی رو میشه با proxychains3 فراخوانی کرد. شاید باید رویکرد اضافه کردن -ng به ته اسم رو امتحان کنیم؟ اگرچه ایده‌آل نیست.

[Davoodeh]

@niyumard just spoke my mind. I go with a totally new name however. Something like jalali instead of a suffix or what not. Replacing the original package and even naming this repository exactly as jcal is the best strategy out there if I'm being honest.

However, I don't blame them, this repository barely has any difference and the development and maintenance is somewhat stalled. There are a lot to be done here. I'm no expert here and just thinking out loud, no experience with packaging or else, just I suggest we keep it like this, make enough changes and when divergent enough with changes worth sharing, then decide on what to call it or how to share it.

[XanderLeaDaren]

As of today, I’ve contacted Fedora jcal maintainers to let them know of the issue, hoping they’ll move to this fork, allowing users to display the correct date.

EDIT (roughly a week after): Fedora jcal maintainer answered to my request saying they’ll try to update ASAP.

Hopefully this means the solution could be to contact jcal package maintainers in other distros, explaining clearly the situation, to have the problem solved! 👍🏽