From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] account for non-existant update-*-database
Date: Sun, 10 Feb 2008 21:24:42 +0100 [thread overview]
Message-ID: <1202675082.7664.111.camel@violet> (raw)
In-Reply-To: <20080210195148.GC2605@esaurito.net>
Hi Filippo,
> > > I've noticed a bug in bluez-gnome when update-*-database programs are not
> > > present (i.e. $UPDATE_*_DATABASE is "" thus install-data-hook fails), the
> > > following patch (or something similar) should work:
> >
> > call --disable-*-update should be a good thing for packages. And then
> > have some post-install routines. Not doing the update is really a
> > problem, because it limits the functionality. So producing an error
> > seems fine to me.
>
> I agree, note though that in this case the error is "permission denied" since
> make will try to execute a directory (e.g. $(DESTDIR)$(datadir)/mime) when
> UPDATE_*_DATABASE is "" which is not much straightforward.
I put something in the CVS now that should fix it. Please test it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-10 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 18:33 [Bluez-devel] [PATCH] account for non-existant update-*-database Filippo Giunchedi
2008-02-10 18:57 ` Marcel Holtmann
2008-02-10 19:51 ` Filippo Giunchedi
2008-02-10 20:24 ` Marcel Holtmann [this message]
2008-02-10 21:40 ` Filippo Giunchedi
2008-02-10 21:56 ` Marcel Holtmann
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=1202675082.7664.111.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox