From: Arvin Schnell <aschnell@suse.de>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Snapper packages for Ubuntu
Date: Tue, 10 Apr 2012 15:36:59 +0200 [thread overview]
Message-ID: <20120410133659.GA14935@suse.de> (raw)
In-Reply-To: <CAG1y0scsfBjVBAL8EQFKJGoR=Dm2K11E8MJLcmqq=gckb0kG2g@mail.gmail.com>
On Tue, Apr 10, 2012 at 08:08:15PM +0700, Fajar A. Nugraha wrote:
> On Tue, Apr 10, 2012 at 6:50 PM, Arvin Schnell <aschnell@suse.de> wro=
te:
> > libblocxx is not required for snapper anymore since about a
> > month. It's checked during configure.
>=20
> You're right. I just tested it, and not having libblocxx during
> compilation results in less dependencies (namely libblocxx itself,
> plus libssl, libcrypto, and libpcre).
>=20
> What functionality, if any, is not available when not using libblocxx=
?
> Since it's still used when present during configure, I assume it's
> good for something.
It's just used for logging. With blocxx an application linking
libsnapper can use blocxx functions to control and redirect
logging.
Regards,
Arvin
--=20
Arvin Schnell, <aschnell@suse.de>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6=
rffer, HRB 16746 (AG N=FCrnberg)
Maxfeldstra=DFe 5
90409 N=FCrnberg
Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-04-10 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 10:37 Snapper packages for Ubuntu Fajar A. Nugraha
2012-04-10 11:50 ` Arvin Schnell
2012-04-10 13:08 ` Fajar A. Nugraha
2012-04-10 13:36 ` Arvin Schnell [this message]
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=20120410133659.GA14935@suse.de \
--to=aschnell@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.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;
as well as URLs for NNTP newsgroup(s).