-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How is f2c maintained? #1
Comments
I found https://netlib.org/f2c/ |
Yes, I know this. It however doesn't look maintained: No contact email is given, and the last modification was on 11 March 2019, while this repository has version 20200916. |
For what it's worth, https://netlib.org/f2c/changes has an update from 2021:
|
OK, but what is the upstream contact? dmg at acm.org as in the README? |
Yeah, I'm jjust the Debian f2c maintainer. I've been walking the line between tracking upstream (who hates modernity) and a reasonable build system and more up-to-date C code. Regarding this particular repo, I occasionally download the upstream tarball and import any changes. I try to keep it a mirror of upstream, along with https://salsa.debian.org/debian/libf2c2.git which holds the corresponding f2c library. See There is also https://github.com/barak/f2c-1.git where I put the f2c and libf2c sources into subdirs, and added an autoconf-based build system, and maybe a little more aggressive about tweaking the code. All around: PATCHES WELCOME!!! |
Hi,
this seems to be a Debian packaging repository for f2c. However, I couldn't find a proper (maintained) upstream.
I've got a few patches that were created by maintaining IRAF where upstream could benefit. Most relevant is iraf-community/iraf@0509cec.
Could you give me a hint how to push this to the proper place?
Best
Ole
(also Debian maintainer of IRAF)
The text was updated successfully, but these errors were encountered: