Skip to content
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

All coin-or ports are conflicting with the maintainer guidelines. #29403

Closed
Neumann-A opened this issue Feb 2, 2023 · 7 comments
Closed

All coin-or ports are conflicting with the maintainer guidelines. #29403

Neumann-A opened this issue Feb 2, 2023 · 7 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support Stale

Comments

@Neumann-A
Copy link
Contributor

The following ports:
coinutils, clp, cgl, osi, openmvg(?)
are conflicting with maintainer guidelines.

a) vendored CMakeLists.txt (upstream also doesn't seem eager to add it coin-or/CoinUtils#101)
b) exported targets not namespaced with unoffical::
c) no pc files from original build system
d) port names don't reflect entries in https://repology.org (those are typically prefixed with coin-or-)

So I vote to remove those ports from the version db and move them to their correct names while at the same time moving them to their upstream buildsystem.

The reason i discovered this is because i wanted to add coin-or-ipopt

@dg0yt
Copy link
Contributor

dg0yt commented Feb 2, 2023

I experimented with the upstream autotools build system for coinutils in #26524.
The problem is that it uses such heavy customizations of autotool that they are bound to specific version of each autothing. They are lagging behind current versions, and we can't autoreconf easily, and so we can't easily get improvements need for uwp et al.

@Neumann-A
Copy link
Contributor Author

#29398 works for x64-windows. Uwp looks a bit sketchy maybe there is just an include missing but otherwise I'll consider it unsupoorted by upstream. don't know about the linux error yet.

@Neumann-A
Copy link
Contributor Author

also maybe I was lucky that they seem to have updated autotools yesterday.

@LilyWangLL LilyWangLL added the category:port-bug The issue is with a library, which is something the port should already support label Feb 3, 2023
@github-actions
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Aug 31, 2023
@LilyWangLL LilyWangLL removed the Stale label Sep 4, 2023
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Mar 30, 2024
@Neumann-A
Copy link
Contributor Author

stll relevant

@github-actions github-actions bot removed the Stale label Apr 1, 2024
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Sep 28, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support Stale
Projects
None yet
Development

No branches or pull requests

3 participants