Invalid startup script for dnsmasq on macOS #461
Comments
|
Yes, the rc.d startup scripts that come with many packages are not intended for macOS at all - they work on BSD systems, and SMF manifests are often present for Illumos/SunOS systems. Unfortunately there's no general support for launchd in pkgsrc, so until that is implemented, it's probably not worth investing time in providing a plist for dnsmasq. Sadly I'm not aware of anyone working on launchd support at this point. |
jperkin
pushed a commit
that referenced
this issue
Mar 20, 2017
Version 2.2 ----------- Released on February 27, 2017, codename Dubnium - Minimum SQLAlchemy version is 0.8 due to use of ``sqlalchemy.inspect``. - Added support for custom ``query_class`` and ``model_class`` as args to the ``SQLAlchemy`` constructor. (`#328`_) - Allow listening to SQLAlchemy events on ``db.session``. (`#364`_) - Allow ``__bind_key__`` on abstract models. (`#373`_) - Allow ``SQLALCHEMY_ECHO`` to be a string. (`#409`_) - Warn when ``SQLALCHEMY_DATABASE_URI`` is not set. (`#443`_) - Don't let pagination generate invalid page numbers. (`#460`_) - Drop support of Flask < 0.10. This means the db session is always tied to the app context and its teardown event. (`#461`_) - Tablename generation logic no longer accesses class properties unless they are ``declared_attr``. (`#467`_) .. _#328: pallets-eco/flask-sqlalchemy#328 .. _#364: pallets-eco/flask-sqlalchemy#364 .. _#373: pallets-eco/flask-sqlalchemy#373 .. _#409: pallets-eco/flask-sqlalchemy#409 .. _#443: pallets-eco/flask-sqlalchemy#443 .. _#460: pallets-eco/flask-sqlalchemy#460 .. _#461: pallets-eco/flask-sqlalchemy#461 .. _#467: pallets-eco/flask-sqlalchemy#467
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
macOS 2016Q4, 64bits.
The dnsmasq package comes with a file (/opt/pkg/share/examples/rc.d/dnsmasq) that is not compatible with macOS. Is there a quick fix for that?
Wouldn't be more "native" for macOS packages to offer a launchctl(plist) example too?
The text was updated successfully, but these errors were encountered: