From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: "Fajar A. Nugraha" <list@fajar.net>,
Tomasz Chmielewski <tch@virtall.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: latest btrfs-progs and asciidoc dependency
Date: Fri, 6 Jun 2014 09:13:37 +0800 [thread overview]
Message-ID: <539115C1.5020507@cn.fujitsu.com> (raw)
In-Reply-To: <CAG1y0sf8nGuhww7h4P+yGxOBVOV9aQRmLrUV3ZzZ2__5d3UYmw@mail.gmail.com>
-------- Original Message --------
Subject: Re: latest btrfs-progs and asciidoc dependency
From: Fajar A. Nugraha <list@fajar.net>
To: Tomasz Chmielewski <tch@virtall.com>
Date: 2014年06月05日 22:51
> On Thu, Jun 5, 2014 at 9:41 PM, Marc MERLIN <marc@merlins.org> wrote:
>> On Thu, Jun 05, 2014 at 12:52:04PM +0100, Tomasz Chmielewski wrote:
>>> And it looks the dependency is ~1 GB of new packages? O_o
>> That seems painful, but at the same time, the alternative, nroff/troff sucks.
>>
>> Part ofyour problem however seems to be runaway dependencies.
>> You are getting x11 and stuff like libdrm which clearly you shouldn't need.
>> If your disk space is more valuable than your time, I recommend you build
>> asciidoc yourself and you should hopefully end up with less.
>>
>> Or you can also remove asciidoc from the makefile and read the raw files
>> which are readable.
>
> ... or try this
>
> # apt-get install --no-install-recommends asciidoc
>
> If that still doesn't work, AND you have lost of free time, AND
> familiar with debian packaging, then you can use latest available
> debian source, adapt it for latest version, and use opensuse build
> service to compile it.
>
It seems to be distribution related problems. And I use debian seldom,
so I can't provide any help
but such problem doesn't occur to me.
For my daily use distribution(Archlinux), asciidoc has python2,libxslt
and docbook-xsl as dependency.
For my test environment distribution(RHEL7), I install xmlto by yum and
then I compile asciidoc manually.
Maybe dig more about the deb package things may help?
-If it does not help, a VM installed with Archlinux would be better?-
Thanks,
Qu
prev parent reply other threads:[~2014-06-06 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 11:52 latest btrfs-progs and asciidoc dependency Tomasz Chmielewski
2014-06-05 14:41 ` Marc MERLIN
2014-06-05 14:51 ` Fajar A. Nugraha
2014-06-06 1:13 ` Qu Wenruo [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=539115C1.5020507@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
--cc=tch@virtall.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.