Re: Package download statistics

[Freddie Cash <fjwcash@xxxxxxxxx>]

--00235429d2109ff46104dc0f9b89
Content-Type: text/plain; charset=UTF-8

On Mon, May 6, 2013 at 6:20 AM, John Marino <dragonflybsd@marino.st> wrote:

> On 5/6/2013 14:52, Petr Janda wrote:
>
>> Now, the _very_ interesting (and unexpected) part is the less than 2%
>>> pkgsrc
>>> packages usage.
>>> Maybe it's just that pkgng is so much better, maybe it's that pkgsrc
>>> users
>>> prefer to build software from source. Difficult to know.
>>>
>>> In any case, I don't see a reason to continue building pkgsrc packages
>>> with
>>> these numbers.
>>>
>>
>> I wonder if this means clang should be included in base instead of GCC
>> 4.4. Since Ports are a FreeBSD thing, and they have switched to clang,
>> more and more ports are going to build with it.
>>
>
> I'm not making the connection.
> For starters, just because FreeBSD has clang as a system compiler doesn't
> mean they use it to build packages.


Clang is the default compiler for FreeBSD 10, and pkgng is the default
package management tool as well.  Thus, all packages for FreeBSD 10 are
built using Clang, in pkgng format.

Clang is available as a compiler in FreeBSD 9, and pkgng is available as
well.  Both can be enabled via simple entries in /etc/make.conf and
/etc/src.conf.  Anyone is free to enable them and test them.

There was a big push near the end of 2012 to get as many ports are possible
to compile with Clang, and to add entries to port Makefiles to specify GCC
if-and-only-if it wouldn't compile with Clang.

IOW, FreeBSD ports are almost all buildable using Clang, and the ports tree
will default to Clang moving forward.

-- 
Freddie Cash
fjwcash@gmail.com

--00235429d2109ff46104dc0f9b89
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, May 6, 2013 at 6:20 AM, John Marino <span dir=3D"ltr">&lt;<a href=
=3D"mailto:dragonflybsd@marino.st"; target=3D"_blank">dragonflybsd@marino.st=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 5/6/2013 14:52, Petr Ja=
nda wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now, the _very_ interesting (and unexpected) part is the less than 2% pkgsr=
c<br>
packages usage.<br>
Maybe it&#39;s just that pkgng is so much better, maybe it&#39;s that pkgsr=
c users<br>
prefer to build software from source. Difficult to know.<br>
<br>
In any case, I don&#39;t see a reason to continue building pkgsrc packages =
with<br>
these numbers.<br>
</blockquote>
<br>
I wonder if this means clang should be included in base instead of GCC<br>
4.4. Since Ports are a FreeBSD thing, and they have switched to clang,<br>
more and more ports are going to build with it.<br>
</blockquote>
<br></div>
I&#39;m not making the connection.<br>
For starters, just because FreeBSD has clang as a system compiler doesn&#39=
;t mean they use it to build packages.</blockquote><div><br></div><div>Clan=
g is the default compiler for FreeBSD 10, and pkgng is the default package =
management tool as well.=C2=A0 Thus, all packages for FreeBSD 10 are built =
using Clang, in pkgng format.<br>
<br></div><div>Clang is available as a compiler in FreeBSD 9, and pkgng is =
available as well.=C2=A0 Both can be enabled via simple entries in /etc/mak=
e.conf and /etc/src.conf.=C2=A0 Anyone is free to enable them and test them=
.<br><br>
There was a big push near the end of 2012 to get as many ports are possible=
 to compile with Clang, and to add entries to port Makefiles to specify GCC=
 if-and-only-if it wouldn&#39;t compile with Clang.<br><br>IOW, FreeBSD por=
ts are almost all buildable using Clang, and the ports tree will default to=
 Clang moving forward.<br>
</div></div><br>-- <br>Freddie Cash<br><a href=3D"mailto:fjwcash@gmail.com"=
>fjwcash@gmail.com</a>
</div></div>

--00235429d2109ff46104dc0f9b89--