Summary: | dev-lisp/openmcl: version bump (or remove in favour of dev-lisp/clozurecl) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marijn Schouten (RETIRED) <hkbst> |
Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | common-lisp, gentoo, treecleaner |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 506890 | ||
Bug Blocks: |
Description
Marijn Schouten (RETIRED)
![]() recent version ("-* amd64 ppc ppc64") in our overlay. Install targets completely messed up; upstream doesn't provide any install support. I have masked openmcl for removal. We should consider putting clozurecl in main tree. (In reply to Marijn Schouten from comment #2) > I have masked openmcl for removal. We should consider putting clozurecl in > main tree. clozurecl is in the tree and looks like this wasn't finally dropped Original comment about being hopelessly outdated was in 2007. Package is still at that version. (In reply to Marijn Schouten from comment #2) > I have masked openmcl for removal. We should consider putting clozurecl in > main tree. I don't see this mask in profiles/package.mask? The dev-lisp/openmcl homepage redirects to the homepage for clozurecl. The homepage explains how openmcl was renamed to clozurecl. Seems as though we should treeclean dev-lisp/openmcl. Also, I believe we should treeclean dev-lisp/openmcl-build-tools as openmcl is the only reverse dep. CC'ing common-lisp herd so they can confirm that this is OK to treeclean. openmcl was renamed to clozurecl. The only reason why openmcl has not been removed from the tree is that openmcl is ~ppc but clozurecl in the tree is ~amd64 ~x86. It would be great if somebody could check the modern clozurecl on ppc (and, probably, ppc64). It should work. After that, openmcl can be removed immediately. (In reply to Andrey Grozin from comment #5) > openmcl was renamed to clozurecl. The only reason why openmcl has not been > removed from the tree is that openmcl is ~ppc but clozurecl in the tree is > ~amd64 ~x86. It would be great if somebody could check the modern clozurecl > on ppc (and, probably, ppc64). It should work. After that, openmcl can be > removed immediately. Do we keep waiting for that arches or simply mask this for removal? # openmcl has been renamed to clozurecl # Masked for removal in 30 days dev-lisp/openmcl dev-lisp/openmcl-build-tools |