Re: Bug#673565: ftpsync -- where to position indirect binaries

2017-03-03 Thread phil
Le 2017-03-03 10:22, Joerg Jaspert a écrit : On 14600 March 1977, p...@reseau-libre.net wrote: I'm currently starting the packaging of the ftpsync tool, and some of the binaries are for internal purpose of the ftpsync tool only. They should not, as a consequence, be deployed in /usr/(s)bin. A

Re: ftpsync -- where to position indirect binaries

2017-03-03 Thread Joerg Jaspert
On 14600 March 1977, p...@reseau-libre.net wrote: > I'm currently starting the packaging of the ftpsync tool, and some of > the binaries are for internal purpose of the ftpsync tool only. They > should not, as a consequence, be deployed in /usr/(s)bin. Already done, it is in NEW currently (source

Re: ftpsync -- where to position indirect binaries

2017-03-03 Thread Andrey Rahmatullin
On Fri, Mar 03, 2017 at 09:36:51AM +0100, p...@reseau-libre.net wrote: > Hi, > > I'm currently starting the packaging of the ftpsync tool, and some of the > binaries are for internal purpose of the ftpsync tool only. They should not, > as a consequence, be deployed in /usr/(s)bin. > > the FHS say

ftpsync -- where to position indirect binaries

2017-03-03 Thread phil
Hi, I'm currently starting the packaging of the ftpsync tool, and some of the binaries are for internal purpose of the ftpsync tool only. They should not, as a consequence, be deployed in /usr/(s)bin. the FHS says that they should be in /usr/libexec [1] but it seems that it is not the Debian