OK sthen

On 2024/04/26 12:31, Landry Breuil wrote:
> Le Fri, Apr 26, 2024 at 10:49:44AM +0100, Stuart Henderson a écrit :
> > On 2024/04/26 11:14, Landry Breuil wrote:
> > > hi,
> > > 
> > > on a bare machine with only rsync installed, trying to use rrsync
> > > wrapper script fails:
> > > 
> > > env: python3: No such file or directory
> > > rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> > > rsync error: error in rsync protocol data stream (code 12) at io.c(231)
> > > [sender=3.2.7]
> > > 
> > > i know it's a bit unfortunate, but i suppose adding python3 as
> > > RUN_DEPENDS is a bit ... gross ? should it be mentioned in a MESSAGE ? a
> > > README ?
> > > 
> > > Landry
> > > 
> > 
> > I don't really like README for such a small note and don't want to add
> > the run dep for something that many people won't use. Personally I think
> > a quick note in DESCR would be enough but it could be a MESSAGE.
> > 
> > (the error message is pretty obvious though..)
> 
> so, something like this..
> 
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/rsync/Makefile,v
> retrieving revision 1.100
> diff -u -r1.100 Makefile
> --- Makefile  27 Sep 2023 14:18:31 -0000      1.100
> +++ Makefile  26 Apr 2024 10:31:03 -0000
> @@ -1,7 +1,7 @@
>  COMMENT =    mirroring/synchronization over low bandwidth links
>  
>  DISTNAME =   rsync-3.2.7
> -REVISION =   1
> +REVISION =   2
>  CATEGORIES = net
>  HOMEPAGE =   https://rsync.samba.org/
>  
> Index: pkg/DESCR
> ===================================================================
> RCS file: /cvs/ports/net/rsync/pkg/DESCR,v
> retrieving revision 1.5
> diff -u -r1.5 DESCR
> --- pkg/DESCR 10 Oct 2013 12:01:31 -0000      1.5
> +++ pkg/DESCR 26 Apr 2024 10:31:03 -0000
> @@ -12,3 +12,7 @@
>  Flavor: iconv
>      extra dependency, for people wanting to bring files from other OSes with
>      more versatile filenames.
> +
> +To use the rrsync wrapper, python3 should be installed.
> +
> +# pkg_add python3
> 

Reply via email to