Re: ports capable of coping with --relocate?

2016-10-13 Thread David Demelier
2016-10-10 7:39 GMT+02:00 Julian Elischer : > On 9/10/2016 10:35 PM, Julian Elischer wrote: >> >> >> for packages I'm using : >> >> * PKG_DBDIR=/$(FOO)/var/db/pkg pkg add --relocate /$(FOO) $(PKGNAME)* >> >> to build up an image in location "$FOO" that I can tar up and install

Re: ports capable of coping with --relocate?

2016-10-13 Thread Mathieu Arnold
Le 10/10/2016 à 07:35, Julian Elischer a écrit : > for packages I'm using : > > * PKG_DBDIR=/$(FOO)/var/db/pkg pkg add --relocate /$(FOO) $(PKGNAME)* > > to build up an image in location "$FOO" that I can tar up and install > onto a machine. --relocate does not do what you think it does. It

Re: harder and harder to avoid pkg

2016-10-13 Thread Miroslav Lachman
David Demelier wrote on 2016/10/13 14:42: 2016-10-12 10:04 GMT+02:00 Andrea Venturoli : On 10/12/16 09:24, Matthieu Volat wrote: And GNU/Linuxes can be a PITA when you have to track -dev(el) packages (which sometimes really requires -bin, -app or whatever), or worst,

Re: harder and harder to avoid pkg

2016-10-13 Thread RW via freebsd-ports
On Tue, 11 Oct 2016 11:59:47 -0700 Julian Elischer wrote: > As the number of dependencies between packages get ever higher, it > becomes more and more difficult to compile packages and the > dependence on binary precompiled packages is increased. However > binary packages are unsuitable for some

Re: Alternatives to rsync

2016-10-13 Thread Greg 'groggy' Lehey
On Thursday, 13 October 2016 at 18:13:39 +1030, Shane Ambler wrote: > On 13/10/2016 15:09, reko.turja--- via freebsd-ports wrote: >> One of my users is needing rsync like functionality to transfer changed >> contents of some directories between couple of machines. As rsync 3 >> isn't open source,

Re: Alternatives to rsync

2016-10-13 Thread reko.turja--- via freebsd-ports
Thanks a lot for your suggestions! Franco and Shane - I will definitely check cpdup out. Georges suggestion is neat, sadly for this usage pattern zfs isn't ideal - lack of memory, files are transferred between freebsd and linux etc. but it's definitely something I'll have to remember for the

Re: Alternatives to rsync

2016-10-13 Thread Shane Ambler
On 14/10/2016 08:56, Greg 'groggy' Lehey wrote: On Thursday, 13 October 2016 at 18:13:39 +1030, Shane Ambler wrote: On 13/10/2016 15:09, reko.turja--- via freebsd-ports wrote: One of my users is needing rsync like functionality to transfer changed contents of some directories between couple of

Re: Alternatives to rsync

2016-10-13 Thread Eduardo Morras via freebsd-ports
Sorry for commenting on this reply to Greg to answer Shane Ambler, I joined maillist today. On Fri, 14 Oct 2016 09:26:03 +1100 Greg 'groggy' Lehey wrote: > On Thursday, 13 October 2016 at 18:13:39 +1030, Shane Ambler wrote: > > On 13/10/2016 15:09, reko.turja--- via

Re: Alternatives to rsync

2016-10-13 Thread Matthias Andree
Am 13.10.2016 um 07:20 schrieb Peter Beckman: > 2. Why is GPL3 out of the question? Is the user going to resell the > device >as a service? If the user is simply "using" the software, no > disclosure >of other software is necessary. Only if your user is attempting to > "make >money"

Re: Alternatives to rsync

2016-10-13 Thread Shane Ambler
On 13/10/2016 15:09, reko.turja--- via freebsd-ports wrote: One of my users is needing rsync like functionality to transfer changed contents of some directories between couple of machines. As rsync 3 isn't open source, but GPL3 it's out of question in order to keep the system untainted. The

PR commit request

2016-10-13 Thread Yasuhiro KIMURA
Dear committers, Would someone please commit following PR's with maintainter timeout? Bug 212142 - devel/magit: update to 2.8.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212142 Bug 212482 - devel/dash.el: update to 2.13.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212482 Best

Re: Alternatives to rsync

2016-10-13 Thread George Michaelson
If you want block efficient, then zfs is your friend 1) make the 'dir' be a distinct zfs filestore in the zpool 2) run zfssnap on some duty cycle 3) profit seriously: as long as the copy can be maintained readonly, in sync with the source, the block level copy of zfs snapshots under some

Re: portsnap tardis

2016-10-13 Thread Kubilay Kocak
On 13/10/2016 6:58 PM, Randy Bush wrote: > a bunch of my 10.3 systems are whining as follows: > > Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. > Fetching snapshot tag from your-org.portsnap.freebsd.org... done. > Latest snapshot on server is older than what we already have! >

Re: portsnap tardis

2016-10-13 Thread Mark Linimon
On Thu, Oct 13, 2016 at 04:58:56PM +0900, Randy Bush wrote: > Fetching snapshot tag from your-org.portsnap.freebsd.org... done. IIUC there was an outage on this server and it has been fixed. mcl ___ freebsd-ports@freebsd.org mailing list

Re: portsnap tardis

2016-10-13 Thread Randy Bush
>> Fetching snapshot tag from your-org.portsnap.freebsd.org... done. > IIUC there was an outage on this server and it has been fixed. how do we apply for refunds? :) ___ freebsd-ports@freebsd.org mailing list

Re: harder and harder to avoid pkg

2016-10-13 Thread David Demelier
2016-10-12 10:04 GMT+02:00 Andrea Venturoli : > On 10/12/16 09:24, Matthieu Volat wrote: > >> And GNU/Linuxes can be a PITA when you have to track -dev(el) packages >> (which sometimes really requires -bin, -app or whatever), or worst, describe >> to people how they are supposed

Re: qa.sh stripped warning

2016-10-13 Thread Mathieu Arnold
Le 12/10/2016 à 20:15, Kyle Evans a écrit : > Hi, > > On Wed, Oct 12, 2016 at 10:35 AM, Mathieu Arnold wrote: >> The warning will never be turned into errors. Maybe add a comment to the >> makefile saying that files must not be stripped. Maybe a bit like go >> ports do it,

Re: Alternatives to rsync

2016-10-13 Thread Franco Fichtner
> On 13 Oct 2016, at 6:39 AM, reko.turja--- via freebsd-ports > wrote: > > The software should be relatively lightweight - no fullblown mirroring/backup > is needed. Also hints how to achieve similar ends using maybe tar/ssh might > do. Try cpdup(1). Cheers,