All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Stef Bon <stefbon@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Plans for a library for btrfs?
Date: Fri, 29 May 2015 19:31:23 +0500	[thread overview]
Message-ID: <20150529193123.1ecb5d8a@natsu> (raw)
In-Reply-To: <CANXojcyqXUNhWLa4ybGyhXceqLdb3DdvM-TvEtwf-KOM6YOsUQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Wed, 27 May 2015 14:31:28 +0200
Stef Bon <stefbon@gmail.com> wrote:

> This program, which I've called fuse-backup, creates backup subvolumes
> and snapshots by calling an extrenal script, which does something
> like:
> 
> btrfs subvolume snapshot -r %PathToBackup%/ %PathToSnapshot%
> 
> This works perfect, but are there any plans to do this with a library?

If this works perfect, then what is the rationale for needing a library?
Do you see a clear reason aside from any vague "it's supposed to be that way".
In the Unix land it is perfectly normal for programs to call other
self-contained programs to do their self-contained jobs:
http://www.catb.org/esr/writings/taoup/html/ch01s06.html#id2877684
Not everything must to be a library linked into your main executable, some
separation and calling external programs to do stuff such as mkfs or snapshot
management seems perfectly fine and even better from the debug-ability
standpoint.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2015-05-29 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 12:31 Plans for a library for btrfs? Stef Bon
2015-05-27 17:39 ` Duncan
2015-05-29 14:04   ` David Sterba
2015-05-29 14:31 ` Roman Mamedov [this message]
2015-05-29 17:02   ` Goffredo Baroncelli
2015-05-29 19:13 ` Juan Orti Alcaine

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=20150529193123.1ecb5d8a@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stefbon@gmail.com \
    /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.