Re: library porting question - optional python bindings

2016-02-29 Thread Chris Inacio 
On Mon, Feb 29, 2016 at 10:04 PM, Chris H  wrote:

> On Mon, 29 Feb 2016 18:53:37 -0800 "Chris H" 
> wrote
>
> > On Mon, 29 Feb 2016 21:38:40 -0500 Chris Inacio 
> wrote
> >
> > > All,
> > >
> > > I'm trying to build a port definition for a library/application that
> can
> > > optionally include Python bindings.  The library/application generally
> > > depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
> > > enable Python support, then you need a Python interpreter plus
> > > Python-protobufs & python zmq.
> > >
> > > Putting an OPTION of Python in the port file is easy.  Including the
> > > optional Python dependencies (and presumably targets - but I'm not
> that far
> > > yet) seems to be a lot more complicated.  I haven't found anything that
> > > would tell me how I'm supposed to do that.  I have found that I'm
> supposed
> > > to add pyXX prefixes to the python targets.
> > >
> > > Does anyone know of a similar application/library that I can go look
> at?
> > > Is there any documentation on how to solve this?
> > Sure. You've read the Porters Handbook;
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
> > Right? :)
>

I have read through the handbook - although probably not linearly.  I have
read the section on Python in ports.

But the combination of what I'm trying to do - Python as an option - can do
that, but also including extra python library dependencies as an option
doesn't seem straight forward.


> > Other than that, there's a myriad of ports in the ports tree.
> > Almost all of which have (OPTIONAL) requirements. Your keyword
> > here is; depends. :)
> If I understand you correctly; maybe something like;
>
> if ${PORT_OPTIONS:MMYOPTION}
> RUN_DEPENDS=${LOCALBASE}/lib/somelib:${PORTSDIR}/lang/python...
> endif
>
> Same is true for BUILD_DEPENDS
>
>
I was hoping there was some newer / less documented
_PYPACKAGE_DEPENDS variable that would save the day here.  Or
port that someone had worked on and effectively created some Makefile foo
that does the equivalent of my made up variable/macro name.


>
> --Chris
> > >
> > > thanks,
> > > Chris Inacio
> >
> >
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: library porting question - optional python bindings

2016-02-29 Thread Chris H 
On Mon, 29 Feb 2016 18:53:37 -0800 "Chris H"  wrote

> On Mon, 29 Feb 2016 21:38:40 -0500 Chris Inacio  wrote
> 
> > All,
> > 
> > I'm trying to build a port definition for a library/application that can
> > optionally include Python bindings.  The library/application generally
> > depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
> > enable Python support, then you need a Python interpreter plus
> > Python-protobufs & python zmq.
> > 
> > Putting an OPTION of Python in the port file is easy.  Including the
> > optional Python dependencies (and presumably targets - but I'm not that far
> > yet) seems to be a lot more complicated.  I haven't found anything that
> > would tell me how I'm supposed to do that.  I have found that I'm supposed
> > to add pyXX prefixes to the python targets.
> > 
> > Does anyone know of a similar application/library that I can go look at?
> > Is there any documentation on how to solve this?
> Sure. You've read the Porters Handbook;
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
> Right? :)
> Other than that, there's a myriad of ports in the ports tree.
> Almost all of which have (OPTIONAL) requirements. Your keyword
> here is; depends. :)
If I understand you correctly; maybe something like;

if ${PORT_OPTIONS:MMYOPTION}
RUN_DEPENDS=${LOCALBASE}/lib/somelib:${PORTSDIR}/lang/python...
endif

Same is true for BUILD_DEPENDS


--Chris
> > 
> > thanks,
> > Chris Inacio
> 
>


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: library porting question - optional python bindings

2016-02-29 Thread Chris H 
On Mon, 29 Feb 2016 21:38:40 -0500 Chris Inacio  wrote

> All,
> 
> I'm trying to build a port definition for a library/application that can
> optionally include Python bindings.  The library/application generally
> depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
> enable Python support, then you need a Python interpreter plus
> Python-protobufs & python zmq.
> 
> Putting an OPTION of Python in the port file is easy.  Including the
> optional Python dependencies (and presumably targets - but I'm not that far
> yet) seems to be a lot more complicated.  I haven't found anything that
> would tell me how I'm supposed to do that.  I have found that I'm supposed
> to add pyXX prefixes to the python targets.
> 
> Does anyone know of a similar application/library that I can go look at?
> Is there any documentation on how to solve this?
Sure. You've read the Porters Handbook;
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
Right? :)
Other than that, there's a myriad of ports in the ports tree.
Almost all of which have (OPTIONAL) requirements. Your keyword
here is; depends. :)

HTH

--Chris
> 
> thanks,
> Chris Inacio


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

library porting question - optional python bindings

2016-02-29 Thread Chris Inacio 
All,

I'm trying to build a port definition for a library/application that can
optionally include Python bindings.  The library/application generally
depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you
enable Python support, then you need a Python interpreter plus
Python-protobufs & python zmq.

Putting an OPTION of Python in the port file is easy.  Including the
optional Python dependencies (and presumably targets - but I'm not that far
yet) seems to be a lot more complicated.  I haven't found anything that
would tell me how I'm supposed to do that.  I have found that I'm supposed
to add pyXX prefixes to the python targets.

Does anyone know of a similar application/library that I can go look at?
Is there any documentation on how to solve this?

thanks,
Chris Inacio
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

RE: FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

2016-02-29 Thread Enzmann, Alexander R. 
Thanks, that info helps. I can wait a week or so while the fixes swim 
downstream. I can also toggle the machine in question to 10.2 or 10.3 while I 
wait.

Really appreciate the quick feedback. This is one of the things that makes this 
so great.

Xander



Sent with Good (www.good.com)

From: Guido Falsi 
Sent: Monday, February 29, 2016 5:03:55 PM
To: Enzmann, Alexander R.; v...@freebsd.org
Cc: po...@freebsd.org
Subject: Re: FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

On 02/29/16 21:17, Enzmann, Alexander R. wrote:
> Help,
>
> I've been using FreeBSD 11.0 for close to a year, and recently ran into a 
> problem.  Virtualbox-ose has disappeared from the list of packages (e.g., 
> http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/), and when I build from 
> source (portsnap fetch, then make install), virtualbox complains about a 
> version mismatch with the kernel and VMs don't run.
>
> Is this simply a timing thing as VirtualBox is updated to match recent 11.0 
> changes, or will there be a long term problem?
>

FreeBSD head r295983 introduced a problem, later solved in r296075,
which caused building kernel modules from ports to fail. This has also
been reported in bugzilla. [1]

Unluckily the machines building ports for head have been updated to a
revision affected by that problem, so the build for the port has failed.
The package will be available again once the cluster machines are
updated to a newer snapshot unaffected by this bug (I don't know how
often those are updated).

So it's definitely a short term problem, actually already solved in the
repositories, which isn't virtualbox or ports fault either.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207561

--
Guido Falsi 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose-kmod build error

2016-02-29 Thread Ivan Klymenko 
On Thu, 25 Feb 2016 09:46:04 +0100
"O. Hartmann"  wrote:

> On Thu, 25 Feb 2016 09:31:00 +0100
> Tommy Scheunemann  wrote:
> 
> > > Am Wed, 24 Feb 2016 22:04:29 +0200
> > > Ivan Klymenko  schrieb:
> > >
> > >> After update from r295867 to r295994:
> > >>
> > >> ...
> > >
> > > Same here ...
> > >
> > 
> > Hi,
> > 
> > try to disable ccache for building the port. Been running into the
> > same problem and disabling ccache fixed it.
> > 
> > Kind regards  
> 
> Don't use ccache!

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207561

So the problem is not on the ccache ;)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

2016-02-29 Thread Guido Falsi 
On 02/29/16 21:17, Enzmann, Alexander R. wrote:
> Help,
> 
> I've been using FreeBSD 11.0 for close to a year, and recently ran into a 
> problem.  Virtualbox-ose has disappeared from the list of packages (e.g., 
> http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/), and when I build from 
> source (portsnap fetch, then make install), virtualbox complains about a 
> version mismatch with the kernel and VMs don't run.
> 
> Is this simply a timing thing as VirtualBox is updated to match recent 11.0 
> changes, or will there be a long term problem?
> 

FreeBSD head r295983 introduced a problem, later solved in r296075,
which caused building kernel modules from ports to fail. This has also
been reported in bugzilla. [1]

Unluckily the machines building ports for head have been updated to a
revision affected by that problem, so the build for the port has failed.
The package will be available again once the cluster machines are
updated to a newer snapshot unaffected by this bug (I don't know how
often those are updated).

So it's definitely a short term problem, actually already solved in the
repositories, which isn't virtualbox or ports fault either.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207561

-- 
Guido Falsi 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Completely unscientific poll: cfengine, puppet, other?

2016-02-29 Thread Michael Gmelin 


> On 28 Feb 2016, at 20:11, Chris Inacio  wrote:
> 
> Hello all,
> 
> I was considering adding some more support into some tooling/ports for
> FreeBSD and I thought it would probably be good to get configuration
> management support some thought.  So I can understand under certain Linux
> flavors (e.g. RedHat) that puppet is the de facto choice - since the
> distribution packager has chosen one.
> 
> Is there a dominant one for FreeBSD?
> 
> Happy if you would just reply with which one, if any, you use.  If you want
> to add more to the conversation, that's fine.  I understand the mailing
> list I posted this to and the likely audience - as I said I started think
> about this from adding more support into some ports.
> 

We're using ansible to configure our FreeBSD machines (bare metal, bhyve, aws, 
do) and jails on them.

- Michael
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

2016-02-29 Thread Enzmann, Alexander R. 
Help,

I've been using FreeBSD 11.0 for close to a year, and recently ran into a 
problem.  Virtualbox-ose has disappeared from the list of packages (e.g., 
http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/), and when I build from 
source (portsnap fetch, then make install), virtualbox complains about a 
version mismatch with the kernel and VMs don't run.

Is this simply a timing thing as VirtualBox is updated to match recent 11.0 
changes, or will there be a long term problem?

Xander
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Completely unscientific poll: cfengine, puppet, other?

2016-02-29 Thread Matthew D. Fuller 
On Mon, Feb 29, 2016 at 08:34:46AM +0100 I heard the voice of
Marko Cupać, and lo! it spake thus:
> On Sun, 28 Feb 2016 14:11:36 -0500
> Chris Inacio  wrote:
> > Happy if you would just reply with which one, if any, you use.
> 
> For my relatively simple task of occasional push of identical
> configuration files to dozens of jails I use salt.

I'm also using salt somewhat lightly for a bunch of jails.  I'm using
it mostly for the incidentals rather than core (e.g., one jail is a
mail server; salt doesn't touch the config.  But others need
null-client type mail configs; salt does those).  It has its...
quirks, but I'm still using it, so I guess that means it beats doing
everything manually.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: resurrect deprecated port print/pnm2ppa

2016-02-29 Thread Miroslav Lachman 

Kurt Jaeger wrote on 02/29/2016 19:02:

Hi!


Yes, a diff against the port prior to it's deletion. This way it can
be resurrected and patched.


I submitted PR with patch:
   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207468


Thanks, I'm working on it.


Committed. I needed time to figure out the resurrection part.


Thank you very much! :)

Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: resurrect deprecated port print/pnm2ppa

2016-02-29 Thread Kurt Jaeger 
Hi!

> > > Yes, a diff against the port prior to it's deletion. This way it can
> > > be resurrected and patched.
> > 
> > I submitted PR with patch:
> >   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207468
> 
> Thanks, I'm working on it.

Committed. I needed time to figure out the resurrection part.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

graphics/giflib: Update to 5.1.2_1 breaks GIF rendering in Konqueror

2016-02-29 Thread Patrick Hess 
Hi,

After upgrading graphics/giflib from 5.1.1 to 5.1.2_1, Konqueror won't
display GIF images in web pages:

http://www.phess.net/images/giflib-bug.png

On the left hand side, with giflib 5.1.1, everything looks as expected.
On the right hand side, after upgrading giflib to 5.1.2_1, none of the
GIF icons are rendered correctly. Only the Fresh Ports logo and the two
magnifying glass icons are still there (as they're JPEGs, not GIFs).

I personally prefer using Konqueror over that obese Firefox for most of
my web browsing, but it feels like I'm the only one. Is anybody else out
there using Konqueror and can confirm (or disconfirm, for that matter)
this behaviour?

This happens on 10.1-RELEASE-p29, on both amd64 and i386, using packages
from the latest pkg repo. Tried clearing the browser cache, didn't help.
Going back to giflib 5.1.1 "fixed" it for now.

Patrick
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Completely unscientific poll: cfengine, puppet, other?

2016-02-29 Thread Felix Hanley 
On Mon, Feb 29, 2016 at 10:39:56AM +0100, Fernando Herrero Carrón wrote:
> El 28 feb. 2016 8:11 p. m., "Chris Inacio"  escribió:
> >
> > Hello all,
> >
> > I was considering adding some more support into some tooling/ports for
> > FreeBSD and I thought it would probably be good to get configuration
> > management support some thought.  So I can understand under certain Linux
> > flavors (e.g. RedHat) that puppet is the de facto choice - since the
> > distribution packager has chosen one.
> >
> > Is there a dominant one for FreeBSD?
> >
> > Happy if you would just reply with which one, if any, you use.  If you
> want
> > to add more to the conversation, that's fine.  I understand the mailing
> > list I posted this to and the likely audience - as I said I started think
> > about this from adding more support into some ports.
> >
> > Thanks
> > chris inacio
> > ___
> > freebsd-ports@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 
> Ansible?

Not sure if dominant but Ansible is great. Leaves a clean remote machine
and is very flexible.

I used CFEngine for a year or so but most of the time was spent jumping
through hoops just to do (what we thought were) simple tasks. Perhaps we
were just doing it the "wrong way" but I would not say it was intuitive.
It also proved to be buggy on enough occasions that we lost confidence.

We also used Puppet for a while and while Ruby is nice to work with it
gave us headaches with memory usage. That was a while back and things
may have changed.

For now I use Ansible where I can.

-felix


signature.asc
Description: PGP signature

Re: ejabberd 16.01

2016-02-29 Thread Ashish SHUKLA 
On Tue, 23 Feb 2016 17:30:11 +0100, Čiernik Tomáš  said:
| Hello,

| is there any chance to get current version of ejabberd (16.01) into
| ports?

Hi,

I've posted a call-for-testing for this update[1], not sure if you've seen
it. The diff in the original post is outdated now, so please refer to the
latest diff[2].

If you could post a followup to the thread with any issues you experienced
there, that'll be great.

References:
[1]  https://lists.freebsd.org/pipermail/freebsd-ports/2016-February/102299.html
[2]  https://lists.freebsd.org/pipermail/freebsd-ports/2016-February/102311.html

Thanks in advance!

-- 
Ashish SHUKLA  | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
Sent from my Emacs


signature.asc
Description: PGP signature

Re: [CFT] net-im/ejabberd to 16.01

2016-02-29 Thread Ashish SHUKLA 
On Mon, 29 Feb 2016 19:34:09 +0530, ash...@freebsd.org (Ashish SHUKLA) said:

[...]


| https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-01.diff
| sha256 sum: ec71fdd19c752b22271ce6e3f899b966b0017f05fa13532d1decf18478e41b6e

Sigh!

Sorry, posted the old URL. This should be:

https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-02.diff
sha256 sum: ec71fdd19c752b22271ce6e3f899b966b0017f05fa13532d1decf18478e41b6e

-- 
Ashish SHUKLA

“We are all in the gutter, but some of us are looking at the stars.”
   (Oscar Wilde)

Sent from my Emacs


signature.asc
Description: PGP signature

Re: [CFT] net-im/ejabberd to 16.01

2016-02-29 Thread Ashish SHUKLA 
On Mon, 29 Feb 2016 14:37:22 +0100, Matthieu Volat  said:


[...]


| Hmm, I'll be a bit overwhelmed until thursday, I'll check that...

Thanks, and I appreciate it.

[...]

| Thanks, there was another blocking issue for me yesterday, which is the 
ejabberdctl is now in bash.

| If possible, I'd like to make a patch to (optionally) revert to pure sh, as I 
find it a bit sad to go full bash only to read a few parameters...

| I'll keep you informed

Thanks in advance, if you could provide the patch. For now, I have updated the
diff to include dependency on bash, which I apparently missed before :/

New diff:

https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-01.diff
sha256 sum: ec71fdd19c752b22271ce6e3f899b966b0017f05fa13532d1decf18478e41b6e

Thanks!
-- 
Ashish SHUKLA  | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
Sent from my Emacs


signature.asc
Description: PGP signature

Re: [CFT] net-im/ejabberd to 16.01

2016-02-29 Thread Matthieu Volat 

> Le 29 févr. 2016 à 02:01, Ashish SHUKLA  a écrit :
> 
> On Sun, 28 Feb 2016 19:33:53 +0100, Matthieu Volat  said:
> | On Sun, 28 Feb 2016 21:02:59 +0530
> | ash...@freebsd.org (Ashish SHUKLA) wrote:
> 
> [..]
> 
> | Thanks for your work,
> 
> Thank you for taking time to test the diff.
> 
> | On my 10.2/amd64 host, the build failed due to using  types 
> without including it in :
> 
> |   /usr/ports/net-im/ejabberd/work/deps/p1_stringprep/c_src/stringprep.cpp
> 
> Following changeset from the diff file should fix this:
> 
> --8<---cut here---start->8---
> diff -urN 
> /usr/ports/net-im/ejabberd/files/patch-.._deps_p1__stringprep_c__src_stringprep.cpp
>  ejabberd/files/patch-.._deps_p1__stringprep_c__src_stringprep.cpp
> --- 
> /usr/ports/net-im/ejabberd/files/patch-.._deps_p1__stringprep_c__src_stringprep.cpp
>1970-01-01 05:30:00.0 +0530
> +++ ejabberd/files/patch-.._deps_p1__stringprep_c__src_stringprep.cpp 
> 2016-02-28 20:11:00.521409079 +0530
> @@ -0,0 +1,10 @@
> +--- ../deps/p1_stringprep/c_src/stringprep.cpp.orig
>  ../deps/p1_stringprep/c_src/stringprep.cpp
> +@@ -19,6 +19,7 @@
> +  */
> +
> + #include 
> ++#include 
> + #include 
> +
> + #include "uni_data.c"
> --8<---cut here---end--->8---
> 
> Are you sure, the diff was not properly applied. I tried the diff from the
> URL, and applied on net-im/ejabberd and seems to have applied fine, and it
> builds fine too, on 10.2-RELEASE/amd64

Hmm, I'll be a bit overwhelmed until thursday, I'll check that...

> 
> | And it seems the pam module is not installed, again?
> 
> | chmod: /usr/local/lib/erlang/lib/ejabberd-16.01/priv/bin/epam: No such file 
> or directory
> | chown: /usr/local/lib/erlang/lib/ejabberd-16.01/priv/bin/epam: No such
> | file or directory
> 
> This is an oversight on my part. Sorry about this. I have updated the diff to
> refer to the correct path.
> 
> https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-01.diff
> sha256 sum: 7dd1f02da1ccf035f58d857a710787bdc6080d2e2651ca1dd9d1a335a3cc57c8
> 
> If you could functionally test PAM support as well, that'll be great.

Thanks, there was another blocking issue for me yesterday, which is the 
ejabberdctl is now in bash.

If possible, I'd like to make a patch to (optionally) revert to pure sh, as I 
find it a bit sad to go full bash only to read a few parameters...

I'll keep you informed

> 
> Thanks!
> --
> Ashish SHUKLA  | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
> Sent from my Emacs



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Completely unscientific poll: cfengine, puppet, other?

2016-02-29 Thread Fernando Herrero Carrón 
El 28 feb. 2016 8:11 p. m., "Chris Inacio"  escribió:
>
> Hello all,
>
> I was considering adding some more support into some tooling/ports for
> FreeBSD and I thought it would probably be good to get configuration
> management support some thought.  So I can understand under certain Linux
> flavors (e.g. RedHat) that puppet is the de facto choice - since the
> distribution packager has chosen one.
>
> Is there a dominant one for FreeBSD?
>
> Happy if you would just reply with which one, if any, you use.  If you
want
> to add more to the conversation, that's fine.  I understand the mailing
> list I posted this to and the likely audience - as I said I started think
> about this from adding more support into some ports.
>
> Thanks
> chris inacio
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Ansible?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2016-02-29 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
net-mgmt/weathermap | 1.1.1   | 25.1.0
+-+
print/lilypond-devel| 2.19.11 | 2.19.37
+-+
security/zxid   | 1.22| 1.42
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"