From: Thomas Tsai <thomas@nchc.org.tw>
To: Nathan Scott <nscott@aconex.com>
Cc: xfs@oss.sgi.com
Subject: Re: Build xfs 3.0 deb problem
Date: Wed, 8 Apr 2009 11:56:48 +0800 [thread overview]
Message-ID: <20090408115648.efaee933.thomas@nchc.org.tw> (raw)
In-Reply-To: <732332763.3161411239158784001.JavaMail.root@mail-au.aconex.com>
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
tkx for reply soon.
My package name is partclone(partclone.org), like partimage, but I used libxfs to check bitmap/super block and backup xfs partition. It's GPL licensed.
We need GPL tool to backup XFS partition. The partimage can do that but get some problems(not based on the xfs library).
The xfs library you maintained well, and it's why I use xfslibs-dev's liarbry to write backup tool, "partclone.xfs" .
so..., may I use xfslibs-dev to build partclone?
or stop it and remove?
tkx.
Thomas
On Wed, 8 Apr 2009 12:46:24 +1000 (EST)
Nathan Scott <nscott@aconex.com> wrote:
>
> ----- "Thomas Tsai" <thomas@nchc.org.tw> wrote:
>
> > Hello xfs,
> >
> > I get the source tarball and easy run Makepkgs debian
> > The build result look fine but lose some library files like
> > libxfs.a....
> >
> > I really need libxfs-dev to build my package.
> > Please give me a hand, tkx.
>
> What is your package, and what libxfs calls does it make?
> libxfs.a was never intended as a published API, and nothing
> outside xfsprogs should be using it.
>
> cheers.
>
> --
> Nathan
--
Thomas Tsai <thomas@nchc.org.tw>
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-08 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 2:05 Build xfs 3.0 deb problem Thomas Tsai
2009-04-08 2:46 ` Nathan Scott
2009-04-08 3:56 ` Thomas Tsai [this message]
2009-04-08 4:10 ` Nathan Scott
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=20090408115648.efaee933.thomas@nchc.org.tw \
--to=thomas@nchc.org.tw \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox