| Summary: | net-misc/openssh: allow building Apple's fork for keychain support | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sam James <sam> |
| Component: | Current packages | Assignee: | Sam James <sam> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | base-system, prefix |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | OS X | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sam James
2020-11-29 21:46:23 UTC
USE-flag ? (if it builds at all?) I would not be opposed to a USE flag, but ideally the minimal code changed to implement this should be separated out in to a patch. A link to an online repo (is it git? is there a clone URL?) isn't very useful. If you attach a .patch file I can take a look at it, and see how much effort it would be to maintain with future OpenSSH releases. Sam, Apple isn't known for creating clean patches. In this case we really need to know a) if it can be built, and b) what it would entail to make this a patch, and c) if their code is compatible with a clean upstream release. My sense is that if it builds, you probably want to keep it in an overlay, as it will benefit a very small portion of users. Homebrew ran into this as well: https://archive.is/hSB6d#10%25 You're both right, of course. I had a look at this and the dumps on the site aren't particularly new (latest is ~Sept 2019). What *is* promising is that MacPorts seem to have a patchset they use. I'll assign this to myself for now to make clear I'm not expecting anyone to act on this - just as a reminder to look into it more. lots of work, and noone willing to do it AFAICT, so closing for now |