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 wayland
enabled.
libwayland-egl.so from mesa-libs and the extra libraries and headers
from gtk30 adds like
The problem with libcanberra is around pulseaudio and gstreamer. It is also
with how gtk, a Visual Graphical toolkit, is mixed in with an Audio application.
I didn't say you didn't know about it, I was just putting it out there. They've
done a good job of cleaning up and fixing ALSA to work on t
On Wed, Dec 20, 2017 at 5:27 PM, Sid wrote:
> The problem with libcanberra is around pulseaudio and gstreamer. It is
> also with how gtk, a Visual Graphical toolkit, is mixed in with an Audio
> application.
>
> I didn't say you didn't know about it, I was just putting it out there.
> They've done
Hi,
Can a port commiter look into this -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 ?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubs
On 12/20/17 11:49, Stefan Lambrev wrote:
Hi,
Can a port commiter look into this -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 ?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscr
On Wed, 20 Dec 2017 09:20:20 +, Johannes Lundberg stated:
>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 wayland
>enabled.
>
>libwayland-egl.so
>
> The normal scenario would be for FreeBSD to wait until other distros have
> throughly vetted the application/protocol/device/other and then consider
> adding it to the basic FreeBSD structure. Unfortunately, by that time the
> target has moved on and FreeBSD is as all too often late to the part
Version portmaster-3.17.11_9
when you are in the port directory, the portmaster build wrong path
/usr/ports/ports instead of /usr/ports
=
[root@VMS /usr/ports/x11-themes/kf5-oxygen-icons5]# portmaster
===>>> No /usr/ports/ports/Mk
On Wed, Dec 20, 2017 at 09:20:20AM +, 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 wayland
> enabled.
>
> libway
> On 20. Dec 2017, at 13:32, Baptiste Daroussin wrote:
>
>> On Wed, Dec 20, 2017 at 09:20:20AM +, 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 themse
Looking forward to testing Wayland more on FreeBSD.
So yes please!
-Tommi
On Wed, Dec 20, 2017 at 2:56 PM, Michael Gmelin wrote:
>
>
> > On 20. Dec 2017, at 13:32, Baptiste Daroussin wrote:
> >
> >> On Wed, Dec 20, 2017 at 09:20:20AM +, Johannes Lundberg wrote:
> >> Hi
> >>
> >> I want t
On Wed, Dec 20, 2017 at 1:13 PM, antranigv wrote:
> Hi!
>
> Trying to understand the changes that would be made by making wayland=on
> by default.
>
> I see a lot of people moving to Wayland from X, but if we do wayland=on,
> what will this mean to Xorg people? from the first thing I got is larger
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 writable
> from /usr/local to /var (as Miroslav suggested), test and submit the new
> port version.
I think you
Adam Vande More wrote on 2017/12/20 15:12:
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 writable
from /usr/local to /var (as Miroslav suggested), test and submi
On Wed, 20 Dec 2017 09:20:20 + "Johannes Lundberg" said
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 wayland
enabled.
libwayland-egl.so from me
On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:
> On Wed, 20 Dec 2017 09:20:20 + "Johannes Lundberg"
> said
>
>> 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 gt
On Thu, Dec 21, 2017 at 12:23 AM, Johannes Lundberg
wrote:
> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:
> > On Wed, 20 Dec 2017 09:20:20 + "Johannes Lundberg" <
> johal...@gmail.com>
> > said
> >
> >> Hi
> >>
> >> I want to suggest that we enable wayland by default. In current state
> >
I would rather see smaller window managers work with Wayland first.
If gtk2 and gtk3 want to enable it fine. But gtk2 and gtk3 shouldn't be mixed
in with Wayland by default, which is what will happen if it is enabled before
it gets a foothold with other window managers.
__
On 12/20/17 01:20, Johannes Lundberg wrote:
For any Desktop user (as well as embedded devices
like IVI-systems and whatnot), Wayland is the future. There's no
escaping that.
Over the history of its development, Wayland could never clearly answer
the question "What are the benefits of Wayland f
On Wed, 20 Dec 2017 17:13:43 + said
On Wed, 20 Dec 2017 16:23:59 + "Johannes Lundberg"
said
On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:
> On Wed, 20 Dec 2017 09:20:20 + "Johannes Lundberg"
> said
>
>> Hi
>>
>> I want to suggest that we enable wayland by default. In current s
Hi Yuri
To be clear, we're not transitioning to anything, we're simply adding
more options. Compare it to adding a new window manager for X, it
doesn't mean you have to stop using the existing ones...
On Wed, Dec 20, 2017 at 5:39 PM, Yuri wrote:
> On 12/20/17 01:20, Johannes Lundberg wrote:
>>
On Wed, Dec 20, 2017 at 08:12:52AM -0600, Adam Vande More wrote:
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 writable
from /usr/local to /var (as Miroslav sugg
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 writable
>> from /usr/local to /var (as Miroslav suggested), t
I support adding wayland support on by default as well. It
still is WIP in several areas one I have not seen mentioned
yet includes nvidia graphics cards. Needing to rebuild
several ports just to test does seem a bit too much though.
Best regards,
Richard Gallamore
On Wed, Dec 20, 2017 at 11:14 A
Hi,
On Wed, 20 Dec 2017, Johannes Lundberg wrote:
Hi
Personally I see no reason not to make it default on, even with
flavors coming up. For any Desktop user (as well as embedded devices
like IVI-systems and whatnot), Wayland is the future. There's no
escaping that.
and why does everyone thin
Am 20.12.17 um 13:08 schrieb Sergio de Almeida Lenzi:
> Version portmaster-3.17.11_9
> when you are in the port directory, the portmaster build wrong path
> /usr/ports/ports instead of /usr/ports
> =
>
>
>
> [root@VMS /usr/ports/x11-themes/
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 wayland
enabled.
libwayland-egl.so from mesa-libs and the ex
On 12/20/2017 11:49, n...@arrishq.net wrote:
Hi,
On Wed, 20 Dec 2017, Johannes Lundberg wrote:
Hi
Personally I see no reason not to make it default on, even with
flavors coming up. For any Desktop user (as well as embedded devices
like IVI-systems and whatnot), Wayland is the future. There'
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 is
> considered broken, then how, in which way?
You ask "Is it broken?".
I ask "Is there a better way?"
Think about gcc: it was develo
a "little thing"
pkg info portmaster
portmaster-3.17.11_11
Name : portmaster
Version : 3.17.11_11
--
portmaster --version
===>>> Version 3.17.10
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/f
> 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
>
>> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:
>> > On Wed, 20 Dec 2017 09:20:20 + "Johannes Lundberg"
>>
>> > said
>> >
>> >
Am 20.12.2017 um 06:40 schrieb Eugene Grosbein:
> On 20.12.2017 01:03, Matthias Andree wrote:
>
>> Dear Ted, Eugene,
> [skip]
>
> 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 ban
On Wed, Dec 20, 2017 at 3:29 PM, Michael Gmelin wrote:
>
>
> > 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" <
> johal...@gmail.com>
> > said
> >
> >> On Wed, Dec 20, 2017 at 4:08 PM, Ch
On Wed, Dec 20, 2017 at 4:19 PM, Matthias Andree
wrote:
> Am 20.12.2017 um 06:40 schrieb Eugene Grosbein:
> > On 20.12.2017 01:03, Matthias Andree wrote:
> >
> >> Dear Ted, Eugene,
> > [skip]
> >
> > What happened with old good "Tools, not policy" thing?
> >
> >
>
> It's simpler than that, no pol
> 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 libcanberra is around pulseaudio and gstreamer. It is also
> with h
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
>
>> On Wed, Dec 20, 2017 at 4:08 PM, Chris H wrote:
>> > On Wed, 20 Dec 20
Wayland should not be mixed in with other code like gtk3, gtk2, gnome related
programs. This will immediately create bloat.
Wayland does remove a lot of unneeded obsolete code that is in Xorg, that is
put in there by principle, and not much else. If gtk creeps into Wayland, those
benefits will
I have the port for the digital currency. It has 3 parts that install
non-intersecting file sets: daemon, cli, qt-ui. The commonality: same
repository, same build options, same license, mostly same port options.
I am attracted to the idea to use flavors to let users choose which part
do they w
> 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
>> > >> O
On Wed, 20 Dec 2017, Kevin Oberman wrote:
On Wed, Dec 20, 2017 at 4:19 PM, Matthias Andree
wrote:
Am 20.12.2017 um 06:40 schrieb Eugene Grosbein:
On 20.12.2017 01:03, Matthias Andree wrote:
Dear Ted, Eugene,
[skip]
What happened with old good "Tools, not policy" thing?
It's simpler th
On 20 Dec, 2017, at 17:19, Matthias Andree wrote:
Am 20.12.2017 um 06:40 schrieb Eugene Grosbein:
On 20.12.2017 01:03, Matthias Andree wrote:
Dear Ted, Eugene,
[skip]
What happened with old good "Tools, not policy" thing?
It's simpler than that, no policy involved.
The tool had a hollow
On Dec 20, 2017 6:16 PM, "Yuri" wrote:
I have the port for the digital currency. It has 3 parts that install
non-intersecting file sets: daemon, cli, qt-ui. The commonality: same
repository, same build options, same license, mostly same port options.
I am attracted to the idea to use flavors to
On Wed, 20 Dec 2017, Adam Weinberger wrote:
I'm a little unsettled by this discussion, because it is moving into
territory with which we have very little precedent. And the precedent
that it would establish is not wholly within our mandate.
Am I the only one who remembers the kerfuffle over "
Am 21.12.2017 um 06:07 schrieb Adam Weinberger:
>> On 20 Dec, 2017, at 17:19, Matthias Andree
>> wrote:
>>
>> Am 20.12.2017 um 06:40 schrieb Eugene Grosbein:
>>> On 20.12.2017 01:03, Matthias Andree wrote:
>>>
Dear Ted, Eugene,
>>> [skip]
>>>
>>> What happened with old good "Tools, not policy
On 21/12/2017 16:35, Freddie Cash wrote:
> On Dec 20, 2017 6:16 PM, "Yuri" wrote:
>
> I have the port for the digital currency. It has 3 parts that install
> non-intersecting file sets: daemon, cli, qt-ui. The commonality: same
> repository, same build options, same license, mostly same port opti
45 matches
Mail list logo
