Le 21/12/2017 à 03:16, Yuri a écrit :
> Do you think flavors are a good fit for this task?
Flavors is for when a port needs to be built differently multiple times.
From what you are saying, this can be built once and splitted up later,
this is subpackages. For now, you should use options, with wha
Thanks for the explanation, Kevin.
I should have included more background information about what Wayland
is and what turning it on by default means in more detail.
Again to clarify, enabling Wayland by default does not change
anything, it simply adds more options. Similar to adding a X11 window
ma
On 12/21/17 00:17, Mathieu Arnold wrote:
Flavors is for when a port needs to be built differently multiple times.
From what you are saying, this can be built once and splitted up later,
this is subpackages. For now, you should use options, with what most
people need as the default options. You c
Le 21/12/2017 à 09:55, Yuri a écrit :
> On 12/21/17 00:17, Mathieu Arnold wrote:
>> Flavors is for when a port needs to be built differently multiple times.
>> From what you are saying, this can be built once and splitted up later,
>> this is subpackages. For now, you should use options, with what
On 21.12.2017 07:35, Kevin Oberman wrote:
>>> What happened with old good "Tools, not policy" thing?
>>
>> It's simpler than that, no policy involved.
>>
>> The tool had a hollow head, and broke after several years of banging it,
>> and the former tool maker told the public it's out of warranty (n
On 21.12.2017 11:35, Ted Hatfield wrote:
> I think if you choose to drop support for procmail you should do as
> Kevin suggests and give a warning and a firm date when support will stop.
There is nothing to stop. We have plenty software working but maintained by
nobody
and it is not a big deal.
On 21.12.2017 14:24, Matthias Andree wrote:
What happened with old good "Tools, not policy" thing?
>>>
>>> It's simpler than that, no policy involved.
>>>
>>> The tool had a hollow head, and broke after several years of banging it,
>>> and the former tool maker told the public it's out of war
On 12/20/2017 21:47, Niclas Zeising wrote:
> On 12/20/17 10:20, Johannes Lundberg wrote:
>> Hi
>>
>> I want to suggest that we enable wayland by default. In current state
>> having some parts of wayland in ports is basically useless the
>> end-users themselves re-build gtk30 and mesa-libs with wayl
On 12/20/17 23:21, roberth...@rcn.com wrote:
To the list:
I salute X for doing its job, but I have no brand loyalty. If
something comes along that is some combination of a) more robust, b)
faster, and c) as easy to install/manage I'll switch in a heartbeat.
(Smaller footprint wo
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
On 12/20/17 23:21, roberth...@rcn.com wrote:
First off, I'm not trying to bring up any flame... my questions are real
and I'd really welcome good answers.
Yuri writes:
It appears that this is the case of fixing of something (xorg)
that wasn't/isn't broken in the first place. And if it
On Thu, Dec 21, 2017 at 8:37 AM, Sid wrote:
> > Blubee blubeeme
> > I'll work on it but let me get the port in the tree first, then I can
> refine it.
> > Just as i've done with my previous ports.
>
> > Sid
> > a simple program that plays simple sounds like "Ding!"
> > The problem with libcanberr
Hi Loïc,
Am 19.12.2017 um 20:48 schrieb L.Bartoletti:
Hi,
Here's my WIP
https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6
Looks interesting to me.
Do we agree, that the package should be named qwt6-qt[45], and not
qwt-qt[45]?
And shouldn't PORTNAME better be named qwt6 instea
Le 19/12/2017 à 20:48, L.Bartoletti a écrit :
> Hi,
>
> Here's my WIP
>
> https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6
As long as you are defining a default FLAVOR value, do it right:
FLAVOR?= ${FLAVORS:[1]}
There are a few stuffs that could be simplified, this works for both
fl
blubee blubeeme; Mon Dec 11 17:03:10 UTC 2017
> I'm taking a look at soundcard.h in /usr/include/sys/soundcard.h in FreeBSD
> vs the soundcard.h in the offical OSS 4.01
> https://sourceforge.net/p/opensound/git/ci/master/tree/include/soundcard.h
> It seems like there's been a lot of changes betwee
On Wed, Dec 20, 2017 at 08:32:37PM +0100, Stefan Esser wrote:
Am 20.12.17 um 15:12 schrieb Adam Vande More:
On Sat, Dec 16, 2017 at 2:10 PM, Dmytro Bilokha wrote:
Guys, thanks for your help. I've managed to adjust user's homedir
using pkg-install script. Now I'll try to move everything writab
On 21/12/2017 03:19, Michael Gmelin wrote:
On 21. Dec 2017, at 02:14, Chris H wrote:
On Thu, 21 Dec 2017 00:29:40 +0100 "Michael Gmelin" said
On 20. Dec 2017, at 18:50, Chris H wrote:
On Wed, 20 Dec 2017 17:13:43 + said
On Wed, 20 Dec 2017 16:23:59 + "Johannes Lundberg"
said
Am 21.12.2017 um 10:16 schrieb Eugene Grosbein:
> So, you demand we stop shipping any unmaintained software with our Ports &
> Packages?
> Absence of CVEs means nothing and almost any non-trivial software has bugs
> (axiom).
Eugene, these are attempts to distract from the argument, or to mount
> Blubee blubeeme
> I'll look at the libcanberra OSS backend and see if I get get the changes
> upstream then the libcanberra maintainer can update the port.
>> Sid
>> Sooner or later, a drop in replacement for libcanberra needs to be made for
>> all BSD's. It should use ogg files from audio/fre
22.12.2017 9:50, Matthias Andree пишет:
> Am 21.12.2017 um 10:16 schrieb Eugene Grosbein:
>
>> So, you demand we stop shipping any unmaintained software with our Ports &
>> Packages?
>> Absence of CVEs means nothing and almost any non-trivial software has bugs
>> (axiom).
>
> Eugene, these are
20 matches
Mail list logo
