linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: python-btrfs & btrfs-heatmap ebuilds now available for Gentoo
Date: Mon, 23 Jul 2018 17:41:20 +0200	[thread overview]
Message-ID: <e553ccb0-05ff-4001-c928-82b1886c65d9@mendix.com> (raw)
In-Reply-To: <2356e8d0-3dcd-34c5-bfc7-b01340fc9cef@applied-asynchrony.com>

On 07/23/2018 04:25 PM, Holger Hoffstätte wrote:
> 
> I wanted to migrate my collection of questionable shell scripts for btrfs
> maintenance/inspection to a more stable foundation and therefore created
> Gentoo ebuilds for Hans van Kranenburg's excellent python-btrfs [1] and
> btrfs-heatmap [2] packages.
> 
> They can be found in my overlay at:
> 
> https://github.com/hhoffstaette/portage/tree/master/sys-fs/python-btrfs
> https://github.com/hhoffstaette/portage/tree/master/sys-fs/btrfs-heatmap

Thanks for doing this!

And now you're making us curious about those
not-so-questionable-any-more scripts. :D

> Both are curently only available for python-3.6 since a change in 3.7
> broke the existing python API [3]. As soon as that is fixed I'll add 3.7
> to the PYTHON_COMPAT entries.

Yes, thanks for testing, I'll have a look at it and will probably also
ask you to help testing the fix.

> btrfs-heatmap properly uses the python-exec wrapper and therefore works
> regardless of currently selected default python version.  :)
> 
> I hope this is useful to someone.

I bet it will. ;-]

-- 
Hans van Kranenburg

      reply	other threads:[~2018-07-23 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 14:25 python-btrfs & btrfs-heatmap ebuilds now available for Gentoo Holger Hoffstätte
2018-07-23 15:41 ` 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=e553ccb0-05ff-4001-c928-82b1886c65d9@mendix.com \
    --to=hans.van.kranenburg@mendix.com \
    --cc=holger@applied-asynchrony.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).