[Nut-upsdev] building on OS X (was: libconf branch build failure: sigemptyset())

[Arnaud Quette]

Hey there

that's a long time since I've been away from the ML (though still acting a
bit in the shadow)!
I'll still be away from the ML, and NUT in general due to personal /
professional constraints.
thus answers awaiting from me will be lagging a bit more...
I'm doing my best to find a solution.

anyway, I've a bit of time, energy and interest to reply to the present one

2013/3/11 Charles Lepple <clepple at gmail.com>

> On Mar 11, 2013, at 5:07 AM, <VaclavKrpec at Eaton.com> wrote:
>
> > Do you by any chance have a list of package names
> > for the OS X (mine is just a fresh clean installation)?
>
> For a basic build test, you can install the Xcode command line tools from
> the Apple developer site or the App store. The base OS seems to have all of
> the headers and libraries needed for OpenSSL and NetSNMP.
>
> For USB, NEON and other libraries, you need Fink or MacPorts. I prefer
> Fink, since it uses the familiar dpkg under the hood, but MacPorts is a
> little more flexible in other areas, since it has a Gentoo-like variants
> system. Along these lines, Fink strives to have every built .deb package be
> the same (variants are implemented by building and installing
> differently-named .deb files), whereas MacPorts allows the packages to be
> different depending on which options were selected. Fink also keeps out of
> /usr/local, since many ported Mac applications drop old versions of
> libraries there.
>
> You can have both installed at once, but it is only recommended to have
> one active in $PATH when building.
>
> Fink: http://www.finkproject.org/ or http://sf.net/projects/fink
>
> MacPorts: http://www.macports.org/
>
> > I'd also appreciate an advice on the packages source and
> > an overview of OS X packaging system (I suppose it has some
> > but I've never worked with it, before).
>
>
maybe a good time to integrate Mac packaging files into the tree?!

Aside from Fink and MacPorts, we haven't focused on the OS X Installer.app
> system since we don't have any GUI applications,


work started by Emilien with Hazelnut:
https://github.com/balooloo/hazelnut


> and because Installer.app really isn't so much of a package manager, just
> an installer. (It records what files are owned by which package, but there
> is no interface to remove packages, handle conflicts, etc.)
>

I would add that .pkg are more suitable for system daemons and apps spreads
across the system
while .app are more suitable for standalone program such as UIs, as
detailed below by Charles

@Vasek: if you're out of (urgent) work, tell me so and I'll point you a few
practical examples for generating .pkg

A typical Mac app is removed by deleting the *.app directory, but a
> command-line tool like NUT would be spread across several directories
> hard-coded at build time. It is possible to change the shared library (.so
> -> .dylib) paths to reference files in a local .app directory for a GUI
> tool, so that's something to think about for the future.
>
> There is also an init replacement called launchd which we would probably
> want use to start upsd and upsmon. (There have been a few posts to this
> list about it.) I have a few attempts at patches to support generating a
> launchd .plist file in my local Git tree, but they need to hook into
> autoconf to get the install pathnames.


-- arno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20130312/3d88af06/attachment.html>