public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Jauhien Piatlicki <jpiatlicki@gmail.com>
Subject: Re: [gentoo-dev] Add support for rsync patches
Date: Wed, 05 Feb 2014 03:13:01 -0500	[thread overview]
Message-ID: <2242447.mC1FDm2MVb@vapier> (raw)
In-Reply-To: <52F15AAC.7050606@gmail.com>

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

On Tuesday, February 04, 2014 22:25:00 Jauhien Piatlicki wrote:
> 04.02.14 20:53, Donnie Berkholz написав(ла):
> > On 12:48 Tue 28 Jan     , Michał Górny wrote:
> >> Dnia 2014-01-28, o godz. 11:59:33 Jauhien Piatlicki napisał(a):
> >>> net-misc/rsync upstream provides a tarball with additional patches that
> >>> can be useful for some users. I think it would be nice to have them
> >>> handled automatically by portage using e.g. USE_EXPAND.
> >>> 
> >>> Of course these patches can be just picked by user an applied using
> >>> epatch_user, but I think it would be much easier and convenient to do
> >>> this with just setting a use flag.
> >> 
> >> ...and what do you want from gentoo-dev@? You need someone to file
> >> the bug for ya?
> > 
> > This is not the level of friendliness that is going to welcome potential
> > new contributors into our community.
> 
> I'm reading this list for a long rime, so I'm quiet acquainted with this
> level of friendliness. So do not mind.

being used to it does not make it acceptable

> I've wrote this list because potential changes I want to do include
> adding of new USE_EXPAND that should be discussed here anyway. And there
> can be reasons why this have not done, that I'm not aware of, and
> maintainer of rsync or somebody else could comment here.
> 
> Anyway I still have not ended with those changes and hence still have
> not posted a bug. So do not mind once again. ;-)

i don't see any patches in rsync-3.1.0.  i'd be hesitant to add support for 
them even if they were there ...

i added epatch_user to the ebuild years ago though, so you largely should be 
able to get the same functionality (albeit with a bit ore footwork on your 
side).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-02-05  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 10:59 [gentoo-dev] Add support for rsync patches Jauhien Piatlicki
2014-01-28 11:48 ` Michał Górny
2014-02-04 19:53   ` Donnie Berkholz
2014-02-04 21:25     ` Jauhien Piatlicki
2014-02-05  8:13       ` Mike Frysinger [this message]
2014-02-05 18:48         ` Tim Harder

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=2242447.mC1FDm2MVb@vapier \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=jpiatlicki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox