From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: Tim Walberg <twalberg@comcast.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs Heatmap - v4 ... colors!!
Date: Fri, 3 Feb 2017 15:46:54 +0100 [thread overview]
Message-ID: <e0e66efa-847d-8c2e-f394-1e9a480ab778@mendix.com> (raw)
In-Reply-To: <CAGqmi75eLTyQ6t4MWU6FdE=vSUy4OjfdEUg5Omx0fNQBWNsAwA@mail.gmail.com>
On 02/03/2017 03:36 PM, Timofey Titovets wrote:
>
> ➜ python-btrfs git:(master) ✗ tar -vxf python-btrfs-5-1-any.pkg.tar.xz
> .PKGINFO
> .BUILDINFO
> .MTREE
> usr/
> usr/lib/
> usr/lib/python3.6/
> usr/lib/python3.6/site-packages/
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/
> usr/lib/python3.6/site-packages/btrfs/
> usr/lib/python3.6/site-packages/btrfs/__pycache__/
> usr/lib/python3.6/site-packages/btrfs/utils.py
> usr/lib/python3.6/site-packages/btrfs/ioctl.py
> usr/lib/python3.6/site-packages/btrfs/ctree.py
> usr/lib/python3.6/site-packages/btrfs/crc32c.py
> usr/lib/python3.6/site-packages/btrfs/__init__.py
> usr/lib/python3.6/site-packages/btrfs/__pycache__/utils.cpython-36.pyc
> usr/lib/python3.6/site-packages/btrfs/__pycache__/ioctl.cpython-36.pyc
> usr/lib/python3.6/site-packages/btrfs/__pycache__/ctree.cpython-36.pyc
> usr/lib/python3.6/site-packages/btrfs/__pycache__/crc32c.cpython-36.pyc
> usr/lib/python3.6/site-packages/btrfs/__pycache__/__init__.cpython-36.pyc
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/installed-files.txt
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/PKG-INFO
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/dependency_links.txt
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/top_level.txt
> usr/lib/python3.6/site-packages/btrfs-5-py3.6.egg-info/SOURCES.txt
>
> I think it's building automaticaly by:
> PIP_CONFIG_FILE=/dev/null pip install --isolated --root="$pkgdir"
> --ignore-installed --no-deps btrfs
>
Even better :-)
Thanks,
--
Hans van Kranenburg
prev parent reply other threads:[~2017-02-03 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 19:53 Btrfs Heatmap - v4 ... colors!! Hans van Kranenburg
[not found] ` <20170118003838.GA4136@comcast.net>
2017-01-19 0:08 ` Hans van Kranenburg
2017-02-03 11:25 ` Timofey Titovets
2017-02-03 12:57 ` Hans van Kranenburg
2017-02-03 14:18 ` Timofey Titovets
2017-02-03 14:27 ` Hans van Kranenburg
2017-02-03 14:36 ` Timofey Titovets
2017-02-03 14:46 ` Hans van Kranenburg [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=e0e66efa-847d-8c2e-f394-1e9a480ab778@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
--cc=twalberg@comcast.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).