#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+---------------------- Comment (by uri@…): A semi-related question. Since my patches haven't been accepted yet - I've been forced to maintain a "shadow" openssl port: {{{ ... # For proper functionality of various resources (port groups, mirror # sites, etc.), the primary MacPorts source must always be tagged # "[default]", even if switched from the default "rsync://" URL. file:///Users/ur20980/ports rsync://rsync.macports.org/release/tarballs/ports.tar [default] }}} The problem with that of course is that whenever the "main" openssl port gets an upgrade - it is not propagated to mine. My question is: is it possible to somehow get the benefits of both approaches - receive the regular port updates, and yet have my own patches applied automatically? It would really save me a lot of pain. -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X