Re: workflow question: how do you maintain the port in sync with upstream?

On Sun, Aug 19, 2018, 13:02 Helen Koike wrote: > > > On 08/14/2018 01:09 PM, blubee blubeeme wrote: > > > > > > On Tue, Aug 14, 2018 at 11:33 PM Mathieu Arnold > > wrote: > > > > On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > > > This one is

Re: workflow question: how do you maintain the port in sync with upstream?

On 08/14/2018 11:41 AM, blubee blubeeme wrote: > On Tue, Aug 14, 2018 at 8:56 PM Helen Koike > wrote: > >> >> >> On 08/13/2018 09:50 PM, blubee blubeeme wrote: >>> >>> >>> On Tue, Aug 14, 2018, 08:26 Helen Koike >> > wrote: >>> >>> >>> >>> On 08/13/2018

Re: workflow question: how do you maintain the port in sync with upstream?

On 08/14/2018 01:09 PM, blubee blubeeme wrote: > > > On Tue, Aug 14, 2018 at 11:33 PM Mathieu Arnold > wrote: > > On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > > This one is fairly straight forward, you can simply replace that >

Executables with [ -def __linux__ ]

This is going out to both current and ports in hopes someone can offer some guidance on this issue. I'm porting some code that seems to want to have -def __linux__ when I run the executable with verbose output, take a look below --

Re: net-mgmt/ocsinventory-ng

Hi! > Finally the setup.sh script fails with "cp: ocsreports/*: No such file > or directory". You mentioned ocsreports is not included? Could you > please explain this? Attached to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227550 is the diff for the new port

Re: net-mgmt/ocsinventory-ng

On 8/13/18 5:52 PM, Fernando Apesteguía wrote: Would you give this one a try? https://people.freebsd.org/~fernape/patches/ocsinventory.svndiff It builds on {10.4,11.1}{amd64,i386} and 12i386. Didn't test in other combinations. It's a bit difficult for me to test it at the moment. Thank you