From: Jeremy Kerr <jk@ozlabs.org>
To: openbmc@lists.ozlabs.org
Subject: Re: [PATCH rest-dbus] Add supporting files
Date: Thu, 8 Oct 2015 13:52:29 +0800 [thread overview]
Message-ID: <5616049D.8090804@ozlabs.org> (raw)
In-Reply-To: <1444262679-18773-2-git-send-email-patches@stwcx.xyz>
Hi Brad,
> +PACKAGE=rest-dbus
> +
> +prefix?=/usr/local
> +bin=$(prefix)/usr/bin
> +share=$(prefix)/usr/share/$(PACKAGE)
> +srv=$(prefix)/lib/systemd/system/
We have /usr/ duplicated there in $(bin) and $(share).
You probably want this to work with
make prefix=/usr libdir=/lib
and so using standard path names, this would be
prefix ?= /usr/local
bindir ?= $(prefix)/bin
libdir ?= $(prefix)/lib
datarootdir ?= $(prefix)/share
pkgdatarootdir ?= $(prefix)/share/$(PACKAGE)
servicedir ?= $(libdir)/systemd/system/
> - resource_base = 'resources'
> + resource_base = '/usr/share/rest-dbus/resources'
.. but this breaks if we use a different prefix. How about:
resource_base = os.path.join(os.path.dirname(__file__),
os.pardir, 'share', 'resources')
- which still depends on pkgdatarootdir & bindir, but they're much less
likely to be altered than prefix.
Also: generally, the systemd service definitions are part of the
distribution, rather than upstream. Should we be putting that in the
recipe instead?
Cheers,
Jeremy
next prev parent reply other threads:[~2015-10-08 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 0:04 [PATCH rest-dbus] Add supporting files OpenBMC Patches
2015-10-08 0:04 ` OpenBMC Patches
2015-10-08 5:52 ` Jeremy Kerr [this message]
2015-10-08 0:45 ` Patrick Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5616049D.8090804@ozlabs.org \
--to=jk@ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.