Re: Multiple ffmpeg versions in ports

2016-03-30 Thread Shane Ambler 

On 31/03/2016 10:29, Kevin Oberman wrote:

On Wed, Mar 30, 2016 at 2:39 PM, Ben Woods  wrote:


On 30 March 2016 at 23:28, Ben Woods  wrote:



What do you think about having numerous versions of ffmpeg in ports,
similar to lang/python?




I guess the obvious question is how could it be possible for multiple
ffmpeg versions to be installed at the same time? Is it possible to ensure
the files do not overlap, and that each package is linking against the
correct installed version?

--
From: Benjamin Woods
woods...@gmail.com



Probably speaking out of turn, but we do have ffmpeg0 and ffmpeg in ports
now. For quite some time we had ffmpeg1, as well, but I think all ports
have now moved on, so ffmpeg1 was removed. It would be up to someone to
write he support for a separate ffmpeg3/


ffmpeg, ffmpeg0 and ffmpeg1 when it existed, can all be installed
simultaneously. If you look through the ffmep0 Makefile you will find
it adds a 0 suffix to the binaries, libraries and dirs installed to
prevent conflicts. The ffmpeg configure step supports specifying the
dirs to install into as well as the suffix to add.

It may be time ffmpeg is updated to 3.x and the current ffmepg could be
moved to ffmpeg2. It is only a matter of someone making and maintaining
the port/s for each version, probably more to the point is how many
other ports would need a version other than what is in ffmpeg.

--
FreeBSD - the place to B...Software Developing

Shane Ambler

___
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: Multiple ffmpeg versions in ports

2016-03-30 Thread Kevin Oberman 
On Wed, Mar 30, 2016 at 2:39 PM, Ben Woods  wrote:

> On 30 March 2016 at 23:28, Ben Woods  wrote:
>
> >
> > What do you think about having numerous versions of ffmpeg in ports,
> > similar to lang/python?
> >
>
>
> I guess the obvious question is how could it be possible for multiple
> ffmpeg versions to be installed at the same time? Is it possible to ensure
> the files do not overlap, and that each package is linking against the
> correct installed version?
>
> --
> From: Benjamin Woods
> woods...@gmail.com
>

Probably speaking out of turn, but we do have ffmpeg0 and ffmpeg in ports
now. For quite some time we had ffmpeg1, as well, but I think all ports
have now moved on, so ffmpeg1 was removed. It would be up to someone to
write he support for a separate ffmpeg3/
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: Multiple ffmpeg versions in ports

2016-03-30 Thread Ben Woods 
On 30 March 2016 at 23:28, Ben Woods  wrote:

>
> What do you think about having numerous versions of ffmpeg in ports,
> similar to lang/python?
>


I guess the obvious question is how could it be possible for multiple
ffmpeg versions to be installed at the same time? Is it possible to ensure
the files do not overlap, and that each package is linking against the
correct installed version?

--
From: Benjamin Woods
woods...@gmail.com
___
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"

Multiple ffmpeg versions in ports

2016-03-30 Thread Ben Woods 
Hello ports people,

What do you think about having numerous versions of ffmpeg in ports,
similar to lang/python?

There seems to be a common problem with ffmpeg being a fast moving project,
with backward incompatible API/ABI changes between major versions. This
results in regular difficulties building ports which depend on ffmpeg, and
often ports bundle their own version of ffmpeg to avoid incorrect API
difficulties across different operating systems / distros (e.g. HandBrake,
plexhometheater). Bundled libraries should be avoided where possible to
ensure we can provide clarity on where security vulnerabilities exist (of
which there are a few for ffmpeg). [1]

Whilst the ffmpeg team appear to be supporting 2.5.x, 2.6.x, 2.7.x, 2.8.x
and 3.0.x, we probably only need to maintain a port where it is required
for another port to build correctly. To start with I was thinking we should
simply create multimedia/ffmpeg30, move multimedia/ffmpeg to
multimedia/ffmpeg28, and create a dummy multimedia/ffmpeg which depends on
multimedia/ffmpeg30. Any ports which fail to build against
multimedia/ffmpeg30 can instead require multimedia/ffmpeg28, and we could
add a comment next to the dependency reminding the port maintainer to move
to the later version of ffmpeg once it is supported by the package.

This would likely mean we will have a number of versions of ffmpeg in the
ports system over time, but I think it is the reality that different
packages support different versions of the ffmpeg API/ABI, and it would
help keep track of what is vulnerable / outdated rather than hiding it by
bundled ffmpeg versions.

Thoughts? If the idea is supported, I could prepare a phabricator review of
the proposed changes.

[1] https://www.freebsd.org/doc/en/books/porters-handbook/bundled-libs.html

--
From: Benjamin Woods
woods...@gmail.com
___
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 creep and additional dependencies for net/ntp?

2016-03-30 Thread Cy Schubert 
In message <20160330073631.gd1...@ivaldir.etoilebsd.net>, Baptiste 
Daroussin wr
ites:
> On Tue, Mar 29, 2016 at 11:09:37PM -0700, Cy Schubert wrote:
> >=20
> > Actually nothing has changed. However the net/ntp ./configure script=20
> > detects if additional libraries are already on your system, e.g. libmd5,=
> =20
> > libdns_sd, and uses them. For instance, my laptop has huge collection of=
> =20
> > packages installed to support various GUI environments under X:
> >=20
> Actually we should try to prevent that as much as possible when we can. That
> said ntp configure script is not nice enough to give you a switch to
> enable/disable it.
> 
> but adding:
> CONFIGURE_ENV=3D"ac_cv_header_dns_sd_h=3Dno" when you do not want to build =
> with
> libdns_sd should do the trick.
> 
> I have not tested, just guessed from reading configure.ac

That should work. If you want, you can do it or the next time I'm in there 
I will. As of now it's on my list of things to do.

If  you do it, remember to do both ntp ports.


-- 
Cheers,
Cy Schubert  or 
FreeBSD UNIX:     Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
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"

www/squid changes

2016-03-30 Thread Pavel Timofeev 
Hello!
Can anybody take a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
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"

Re: Library creep and additional dependencies for net/ntp?

2016-03-30 Thread Baptiste Daroussin 
On Tue, Mar 29, 2016 at 11:09:37PM -0700, Cy Schubert wrote:
> 
> Actually nothing has changed. However the net/ntp ./configure script 
> detects if additional libraries are already on your system, e.g. libmd5, 
> libdns_sd, and uses them. For instance, my laptop has huge collection of 
> packages installed to support various GUI environments under X:
> 
Actually we should try to prevent that as much as possible when we can. That
said ntp configure script is not nice enough to give you a switch to
enable/disable it.

but adding:
CONFIGURE_ENV="ac_cv_header_dns_sd_h=no" when you do not want to build with
libdns_sd should do the trick.

I have not tested, just guessed from reading configure.ac

Bapt


signature.asc
Description: PGP signature

Re: Library creep and additional dependencies for net/ntp?

2016-03-30 Thread Dewayne Geraghty 
On 30 March 2016 at 17:09, Cy Schubert  wrote:

> In message
>  om>
> , Dewayne Geraghty writes:
> > --001a114035e2660c5e052f3be038
> > Content-Type: text/plain; charset=UTF-8
> >
> > Overnight I updated /usr/ports via svnlite, rebuilt all ports and noticed
> > additional libraries and dependencies for net/ntp
> >
> > On 12th Feb, I'd built ntp-4.2.8p6.txz.  Checking the libraries, I had
> > # ldd /usr/local/sbin/ntpd
> > /usr/local/sbin/ntpd:
> > libmd.so.6 => /lib/libmd.so.6 (0x280fb000)
> > libm.so.5 => /lib/libm.so.5 (0x2810f000)
> > libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x28139000)
> > libintl.so.8 => /usr/local/lib/libintl.so.8 (0x282ca000)
> > libthr.so.3 => /lib/libthr.so.3 (0x282d3000)
> > libc.so.7 => /lib/libc.so.7 (0x282f4000)
> >
> > Today, I rebuilt ntp and found
> > # ldd /usr/local/sbin/ntpd
> > /usr/local/sbin/ntpd:
> >* libmd5.so.0 => /usr/local/lib/libmd5.so.0 (0x280fc000) - from
> > libwww*
> > libm.so.5 => /lib/libm.so.5 (0x280fe000)
> > libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x28128000)
> >* libdns_sd.so.1 => /usr/local/lib/libdns_sd.so.1 (0x282b9000) -
> > mDNSResponder*
> > libintl.so.8 => /usr/local/lib/libintl.so.8 (0x282c1000)
> > libthr.so.3 => /lib/libthr.so.3 (0x282ca000)
> > libc.so.7 => /lib/libc.so.7 (0x282eb000)
> >
> > *  libz.so.6 => /lib/libz.so.6 (0x2845e000)libssl.so.8 =>
> > /usr/local/lib/libssl.so.8 (0x28473000)*
> >
> > Checking pkg info -d ntpd
> > # pkg info -d ntp
> > ntp-4.2.8p6:
> > openssl-1.0.2_8
> > libevent2-2.0.22_1
> > gettext-runtime-0.19.6
> > libedit-3.1.20150325_1
> >
> > Can anyone shed any light on why ntp has picked up these additional
> > libraries and created additional dependencies on libwww and
> mDNSresponder?
> >
> > I'm also curious as to how *libz *and *libssl *are now required, between
> > ntp4.2.8p6 built in February vs the March build?
> >
> > By way of comparison,
> > /usr/sbin/ntpd:  (base OS ntp also ntp4.2.8p6)
> > libm.so.5 => /lib/libm.so.5 (0x8008d2000)
> > libthr.so.3 => /lib/libthr.so.3 (0x800afa000)
> > libcrypto.so.7 => /lib/libcrypto.so.7 (0x800d1f000)
> > libc.so.7 => /lib/libc.so.7 (0x801115000)
> >
> > These results are on "FreeBSD 10.3-PRERELEASE #0 r296427M:"  My options
> for
> > ntp have remained unchanged since 20140914.
>
> Actually nothing has changed. However the net/ntp ./configure script
> detects if additional libraries are already on your system, e.g. libmd5,
> libdns_sd, and uses them. For instance, my laptop has huge collection of
> packages installed to support various GUI environments under X:
>
> slippy$ ldd /usr/local/sbin/ntpd
> /usr/local/sbin/ntpd:
> libmd5.so.0 => /usr/local/lib/libmd5.so.0 (0x2c4c6000)
> libm.so.5 => /lib/libm.so.5 (0x2c6c8000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x2ca0)
> libdns_sd.so.1 => /usr/local/lib/libdns_sd.so.1 (0x2ce5e000)
> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x2d066000)
> libthr.so.3 => /lib/libthr.so.3 (0x2d271000)
> libc.so.7 => /lib/libc.so.7 (0x2d496000)
> libz.so.6 => /lib/libz.so.6 (0x2d843000)
> libssl.so.7 => /usr/lib/libssl.so.7 (0x2da59000)
> libcrypto.so.7 => /lib/libcrypto.so.7 (0x2dcc5000)
> slippy$
>
> My firewall OTOH bare bones, has very few packages and no X installed:
>
> cwfw# ldd /usr/local/sbin/ntpd
> /usr/local/sbin/ntpd:
> libmd.so.6 => /lib/libmd.so.6 (0x8008ba000)
> libm.so.5 => /lib/libm.so.5 (0x800aca000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800e0)
> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x801253000)
> libthr.so.3 => /lib/libthr.so.3 (0x80145e000)
> libc.so.7 => /lib/libc.so.7 (0x801683000)
> cwfw#
>
> In my poudriere build repo, the cached package (it's still building), ntpd
> references:
>
> cwsys$ ldd /tmp/usr/local/sbin/ntpd
> /tmp/usr/local/sbin/ntpd:
> libmd.so.6 => /lib/libmd.so.6 (0x2c4c4000)
> libm.so.5 => /lib/libm.so.5 (0x2c6d4000)
> libcrypto.so.7 => /lib/libcrypto.so.7 (0x2c8fd000)
> libthr.so.3 => /lib/libthr.so.3 (0x2ccf3000)
> libc.so.7 => /lib/libc.so.7 (0x2cf18000)
> cwsys$
>
> The ntp tarball does this out of the box -- read ./configure. The more
> libraries the ntp build finds, the more it uses. Don't worry about it
> dragging in gratuitous packages. It won't. But, it does use whatever it
> detects.
>
> If you want a minimal build, use poudriere to build your own binary
> packages or use FreeBSD.org built binary packages. (If you're wondering,
> ntpd on my laptop looks as it does because I did a point upgrade of net/ntp
> outside of poudriere built packages.) Generally, it's recommended people
> use binary packages.
>
>

Re: Library creep and additional dependencies for net/ntp?

2016-03-30 Thread Cy Schubert 
In message 
, Dewayne Geraghty writes:
> --001a114035e2660c5e052f3be038
> Content-Type: text/plain; charset=UTF-8
> 
> Overnight I updated /usr/ports via svnlite, rebuilt all ports and noticed
> additional libraries and dependencies for net/ntp
> 
> On 12th Feb, I'd built ntp-4.2.8p6.txz.  Checking the libraries, I had
> # ldd /usr/local/sbin/ntpd
> /usr/local/sbin/ntpd:
> libmd.so.6 => /lib/libmd.so.6 (0x280fb000)
> libm.so.5 => /lib/libm.so.5 (0x2810f000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x28139000)
> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x282ca000)
> libthr.so.3 => /lib/libthr.so.3 (0x282d3000)
> libc.so.7 => /lib/libc.so.7 (0x282f4000)
> 
> Today, I rebuilt ntp and found
> # ldd /usr/local/sbin/ntpd
> /usr/local/sbin/ntpd:
>* libmd5.so.0 => /usr/local/lib/libmd5.so.0 (0x280fc000) - from
> libwww*
> libm.so.5 => /lib/libm.so.5 (0x280fe000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x28128000)
>* libdns_sd.so.1 => /usr/local/lib/libdns_sd.so.1 (0x282b9000) -
> mDNSResponder*
> libintl.so.8 => /usr/local/lib/libintl.so.8 (0x282c1000)
> libthr.so.3 => /lib/libthr.so.3 (0x282ca000)
> libc.so.7 => /lib/libc.so.7 (0x282eb000)
> 
> *  libz.so.6 => /lib/libz.so.6 (0x2845e000)libssl.so.8 =>
> /usr/local/lib/libssl.so.8 (0x28473000)*
> 
> Checking pkg info -d ntpd
> # pkg info -d ntp
> ntp-4.2.8p6:
> openssl-1.0.2_8
> libevent2-2.0.22_1
> gettext-runtime-0.19.6
> libedit-3.1.20150325_1
> 
> Can anyone shed any light on why ntp has picked up these additional
> libraries and created additional dependencies on libwww and mDNSresponder?
> 
> I'm also curious as to how *libz *and *libssl *are now required, between
> ntp4.2.8p6 built in February vs the March build?
> 
> By way of comparison,
> /usr/sbin/ntpd:  (base OS ntp also ntp4.2.8p6)
> libm.so.5 => /lib/libm.so.5 (0x8008d2000)
> libthr.so.3 => /lib/libthr.so.3 (0x800afa000)
> libcrypto.so.7 => /lib/libcrypto.so.7 (0x800d1f000)
> libc.so.7 => /lib/libc.so.7 (0x801115000)
> 
> These results are on "FreeBSD 10.3-PRERELEASE #0 r296427M:"  My options for
> ntp have remained unchanged since 20140914.

Actually nothing has changed. However the net/ntp ./configure script 
detects if additional libraries are already on your system, e.g. libmd5, 
libdns_sd, and uses them. For instance, my laptop has huge collection of 
packages installed to support various GUI environments under X:

slippy$ ldd /usr/local/sbin/ntpd 
/usr/local/sbin/ntpd:
libmd5.so.0 => /usr/local/lib/libmd5.so.0 (0x2c4c6000)
libm.so.5 => /lib/libm.so.5 (0x2c6c8000)
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x2ca0)
libdns_sd.so.1 => /usr/local/lib/libdns_sd.so.1 (0x2ce5e000)
libintl.so.8 => /usr/local/lib/libintl.so.8 (0x2d066000)
libthr.so.3 => /lib/libthr.so.3 (0x2d271000)
libc.so.7 => /lib/libc.so.7 (0x2d496000)
libz.so.6 => /lib/libz.so.6 (0x2d843000)
libssl.so.7 => /usr/lib/libssl.so.7 (0x2da59000)
libcrypto.so.7 => /lib/libcrypto.so.7 (0x2dcc5000)
slippy$ 

My firewall OTOH bare bones, has very few packages and no X installed:

cwfw# ldd /usr/local/sbin/ntpd
/usr/local/sbin/ntpd:
libmd.so.6 => /lib/libmd.so.6 (0x8008ba000)
libm.so.5 => /lib/libm.so.5 (0x800aca000)
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800e0)
libintl.so.8 => /usr/local/lib/libintl.so.8 (0x801253000)
libthr.so.3 => /lib/libthr.so.3 (0x80145e000)
libc.so.7 => /lib/libc.so.7 (0x801683000)
cwfw# 

In my poudriere build repo, the cached package (it's still building), ntpd 
references:

cwsys$ ldd /tmp/usr/local/sbin/ntpd
/tmp/usr/local/sbin/ntpd:
libmd.so.6 => /lib/libmd.so.6 (0x2c4c4000)
libm.so.5 => /lib/libm.so.5 (0x2c6d4000)
libcrypto.so.7 => /lib/libcrypto.so.7 (0x2c8fd000)
libthr.so.3 => /lib/libthr.so.3 (0x2ccf3000)
libc.so.7 => /lib/libc.so.7 (0x2cf18000)
cwsys$ 

The ntp tarball does this out of the box -- read ./configure. The more 
libraries the ntp build finds, the more it uses. Don't worry about it 
dragging in gratuitous packages. It won't. But, it does use whatever it 
detects.

If you want a minimal build, use poudriere to build your own binary 
packages or use FreeBSD.org built binary packages. (If you're wondering, 
ntpd on my laptop looks as it does because I did a point upgrade of net/ntp 
outside of poudriere built packages.) Generally, it's recommended people 
use binary packages.

To summarize, use binary packages. If you want to roll your own, use 
poudriere, the install your own binary packages. Otherwise ports/net/ntp 
will dynamically discover libraries during ./configure it can use.

Hope this helps.


-- 
Cheers,
Cy Schubert