Re: [Slackbuilds-users] qt5 + pulseaudio

[or...@fredslev.dk]

Sorry for the slow reply. I lost interest in pushing this when it
became clear that merging a simple patch required more energy than I
had to expend... Take it or leave it, I'm not interested in fighting
over this.

Previous e-mails were written a while ago and with a previous e-mail
address.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Christoph Willing]

On 10/05/18 09:43, Daniel Prosser wrote:
>>> Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement
> directly to the relevant maintainers. I'm sure such suggestions would
> mostly be adopted provided They don't adversely affect normal systems. 
> 
> Isn't that exactly what Hunter has done?

Yes, bravo Hunter.

However, I was responding to Richard's suggestion for a second set of
SlackBuilds just to accommodate special requirements for ALSA-only users.

chris

> 
> On May 9, 2018 5:53 PM, Christoph Willing 
> wrote:
> 
> On 10/05/18 06:53, Richard Narron wrote:
> > On Tue, 8 May 2018, Matteo Bernardini wrote:
> >
> >> 2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
> >>> That assumption is irrelevant and if a maintainer is not willing to
> >>> respond to bug reports then it should be possible to implement
> fixes
> >>> without the maintainer.
> >>>
> >>> The bottom line is that this patch would make the qt5.SlackBuild
> more
> >>> fail proof and the only reason to not accept it is to spite
> people who
> >>> do not use pulseaudio. This can only have a negative effect on the
> >>> usefulness and reliability of SBo...
> >>
> >> we have different opinion on what is a bug an what are legit
> >> maintainer decisions.
> >> optional pulseaudio support is surely not a bug: pulseaudio is not
> >> optional at all in slackware 14.2 and I explained why we cannot
> >> consider it optional even in the next Slackware release: stuff in
> >> /extra is not part of a Slackware full installation and we support
> >> just that.
> >> that said, is up to the maintainer if they want to add a switch in
> >> their SlackBuilds to make pulseaudio optional (with pulseaudio
> enabled
> >> by default, of course), and it's up to the users to use it (under
> >> their own responsibility) or not.
> >
> > I would suggest that the alsa files in /extra are not actually
> "extra".
> > They are replacements for standard pulseaudio Slackware current
> packages.
> >
> > It would be hard for someone with with pulseaudio to test the alsa
> side of
> > things and hard for someone with alsa to test the pulseaudio side of
> > things.
> >
> > So instead of an alsa-pulseaudio switch perhaps we should allow
> two sets
> > of packages, the standard ones with pulseaudio and another set
> with alsa.
> >
> 
> How would that make testing any easier for a maintainer - or are you
> suggesting having multiple maintainers too? It sounds like a lot of
> complication just for the sake of the few SlackBuilds that would
> actually be involved.
> 
> No doubt alsa enthusiasts are smart enough to make their own changes in
> cases where the maintainer hasn't adopted some pulseaudio/alsa switch
> arrangement.
> 
> Hint to alsa-enthusiasts:
>     suggest your alsa-tested switch arrangement directly to the
> relevant
> maintainers. I'm sure such suggestions would mostly be adopted provided
> they don't adversely affect normal systems.
> 
> chris
> 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
> 
> 
> 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Daniel Prosser]

>> Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement 
>> directly to the relevant maintainers. I'm sure such suggestions would mostly 
>> be adopted provided They don't adversely affect normal systems.

Isn't that exactly what Hunter has done?

On May 9, 2018 5:53 PM, Christoph Willing  wrote:

On 10/05/18 06:53, Richard Narron wrote:
> On Tue, 8 May 2018, Matteo Bernardini wrote:
>
>> 2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
>>> That assumption is irrelevant and if a maintainer is not willing to
>>> respond to bug reports then it should be possible to implement fixes
>>> without the maintainer.
>>>
>>> The bottom line is that this patch would make the qt5.SlackBuild more
>>> fail proof and the only reason to not accept it is to spite people who
>>> do not use pulseaudio. This can only have a negative effect on the
>>> usefulness and reliability of SBo...
>>
>> we have different opinion on what is a bug an what are legit
>> maintainer decisions.
>> optional pulseaudio support is surely not a bug: pulseaudio is not
>> optional at all in slackware 14.2 and I explained why we cannot
>> consider it optional even in the next Slackware release: stuff in
>> /extra is not part of a Slackware full installation and we support
>> just that.
>> that said, is up to the maintainer if they want to add a switch in
>> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled
>> by default, of course), and it's up to the users to use it (under
>> their own responsibility) or not.
>
> I would suggest that the alsa files in /extra are not actually "extra".
> They are replacements for standard pulseaudio Slackware current packages.
>
> It would be hard for someone with with pulseaudio to test the alsa side of
> things and hard for someone with alsa to test the pulseaudio side of
> things.
>
> So instead of an alsa-pulseaudio switch perhaps we should allow two sets
> of packages, the standard ones with pulseaudio and another set with alsa.
>

How would that make testing any easier for a maintainer - or are you
suggesting having multiple maintainers too? It sounds like a lot of
complication just for the sake of the few SlackBuilds that would
actually be involved.

No doubt alsa enthusiasts are smart enough to make their own changes in
cases where the maintainer hasn't adopted some pulseaudio/alsa switch
arrangement.

Hint to alsa-enthusiasts:
suggest your alsa-tested switch arrangement directly to the relevant
maintainers. I'm sure such suggestions would mostly be adopted provided
they don't adversely affect normal systems.

chris

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Christoph Willing]

On 10/05/18 06:53, Richard Narron wrote:
> On Tue, 8 May 2018, Matteo Bernardini wrote:
> 
>> 2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
>>> That assumption is irrelevant and if a maintainer is not willing to
>>> respond to bug reports then it should be possible to implement fixes
>>> without the maintainer.
>>>
>>> The bottom line is that this patch would make the qt5.SlackBuild more
>>> fail proof and the only reason to not accept it is to spite people who
>>> do not use pulseaudio. This can only have a negative effect on the
>>> usefulness and reliability of SBo...
>>
>> we have different opinion on what is a bug an what are legit
>> maintainer decisions.
>> optional pulseaudio support is surely not a bug: pulseaudio is not
>> optional at all in slackware 14.2 and I explained why we cannot
>> consider it optional even in the next Slackware release: stuff in
>> /extra is not part of a Slackware full installation and we support
>> just that.
>> that said, is up to the maintainer if they want to add a switch in
>> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled
>> by default, of course), and it's up to the users to use it (under
>> their own responsibility) or not.
> 
> I would suggest that the alsa files in /extra are not actually "extra".
> They are replacements for standard pulseaudio Slackware current packages.
> 
> It would be hard for someone with with pulseaudio to test the alsa side of
> things and hard for someone with alsa to test the pulseaudio side of
> things.
> 
> So instead of an alsa-pulseaudio switch perhaps we should allow two sets
> of packages, the standard ones with pulseaudio and another set with alsa.
> 

How would that make testing any easier for a maintainer - or are you
suggesting having multiple maintainers too? It sounds like a lot of
complication just for the sake of the few SlackBuilds that would
actually be involved.

No doubt alsa enthusiasts are smart enough to make their own changes in
cases where the maintainer hasn't adopted some pulseaudio/alsa switch
arrangement.

Hint to alsa-enthusiasts:
suggest your alsa-tested switch arrangement directly to the relevant
maintainers. I'm sure such suggestions would mostly be adopted provided
they don't adversely affect normal systems.

chris

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Richard Narron]

On Tue, 8 May 2018, Matteo Bernardini wrote:

> 2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
> > That assumption is irrelevant and if a maintainer is not willing to
> > respond to bug reports then it should be possible to implement fixes
> > without the maintainer.
> >
> > The bottom line is that this patch would make the qt5.SlackBuild more
> > fail proof and the only reason to not accept it is to spite people who
> > do not use pulseaudio. This can only have a negative effect on the
> > usefulness and reliability of SBo...
>
> we have different opinion on what is a bug an what are legit
> maintainer decisions.
> optional pulseaudio support is surely not a bug: pulseaudio is not
> optional at all in slackware 14.2 and I explained why we cannot
> consider it optional even in the next Slackware release: stuff in
> /extra is not part of a Slackware full installation and we support
> just that.
> that said, is up to the maintainer if they want to add a switch in
> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled
> by default, of course), and it's up to the users to use it (under
> their own responsibility) or not.

I would suggest that the alsa files in /extra are not actually "extra".
They are replacements for standard pulseaudio Slackware current packages.

It would be hard for someone with with pulseaudio to test the alsa side of
things and hard for someone with alsa to test the pulseaudio side of
things.

So instead of an alsa-pulseaudio switch perhaps we should allow two sets
of packages, the standard ones with pulseaudio and another set with alsa.

Maybe have a naming convention or separate directory?

Richard Narron
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Andrzej Telszewski]

On 09/05/18 00:12, Christoph Willing wrote:

In my case, I use git branches to accommodate the different SlackBuild
versions I want to maintain. Apart from the branches connected with
SlackBuilds for which I am the maintainer (therefore conforming strictly
to SBo conventions), I have a separate branch which contains all the
changes in the various SlackBuilds that I use for my local systems. At
each SBo update, I rebase that separate branch to master so that the
branch is up to date but local changes remain intact. Occasionally the
rebase will conflict with a change in the branch but that's easily fixed.


I do the exact same thing.
Works very well.
Thanks for wording it up. :-)

--
Best regards / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Christoph Willing]

On 08/05/18 05:53, or...@fredslev.dk wrote:
[snip]
> It would really mean a lot to me
> if this was applied to qt5 too so I that I didn't constantly have to
> edit the SlackBuild every time I update or rebuild qt5. Something which
> I routinely forget to do until the build fails...
> 

Many (most?) of us have at least one SlackBuild which we change to suit
personal requirements. No doubt, those who have multiple SlackBuilds in
this category also have some strategy to work through these differences
with minimal pain whenever there is an update.

In my case, I use git branches to accommodate the different SlackBuild
versions I want to maintain. Apart from the branches connected with
SlackBuilds for which I am the maintainer (therefore conforming strictly
to SBo conventions), I have a separate branch which contains all the
changes in the various SlackBuilds that I use for my local systems. At
each SBo update, I rebase that separate branch to master so that the
branch is up to date but local changes remain intact. Occasionally the
rebase will conflict with a change in the branch but that's easily fixed.

chris
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Matteo Bernardini]

2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
> That assumption is irrelevant and if a maintainer is not willing to
> respond to bug reports then it should be possible to implement fixes
> without the maintainer.
>
> The bottom line is that this patch would make the qt5.SlackBuild more
> fail proof and the only reason to not accept it is to spite people who
> do not use pulseaudio. This can only have a negative effect on the
> usefulness and reliability of SBo...

we have different opinion on what is a bug an what are legit
maintainer decisions.
optional pulseaudio support is surely not a bug: pulseaudio is not
optional at all in slackware 14.2 and I explained why we cannot
consider it optional even in the next Slackware release: stuff in
/extra is not part of a Slackware full installation and we support
just that.
that said, is up to the maintainer if they want to add a switch in
their SlackBuilds to make pulseaudio optional (with pulseaudio enabled
by default, of course), and it's up to the users to use it (under
their own responsibility) or not.

Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[or...@fredslev.dk]

That assumption is irrelevant and if a maintainer is not willing to
respond to bug reports then it should be possible to implement fixes
without the maintainer.

The bottom line is that this patch would make the qt5.SlackBuild more
fail proof and the only reason to not accept it is to spite people who
do not use pulseaudio. This can only have a negative effect on the
usefulness and reliability of SBo...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Larry Hajali]

Hi,

> I e-mailed a very small patch to the qt5.SlackBuild maintainer more
> than once to allow dynamically detecting if pulseaudio is installed with
> pkg-config and disabling it if its not. However its been a few weeks
> since my last attempt and much longer for the previous ones. I have
> received absolutely 0 replies.
>
I only see one email from you in my inbox on April 22.  I haven't replied
as I started a new job and life has gotten in the way.

Can this be done? I've attached the patch to this e-mail.
>
I'll look at the patch this weekend.

--Larry
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 + pulseaudio

[Matteo Bernardini]

2018-05-07 21:53 GMT+02:00 or...@fredslev.dk :
> Hi,
>
> I e-mailed a very small patch to the qt5.SlackBuild maintainer more
> than once to allow dynamically detecting if pulseaudio is installed with
> pkg-config and disabling it if its not. However its been a few weeks
> since my last attempt and much longer for the previous ones. I have
> received absolutely 0 replies.
>
> I also e-mailed a similar patch to Pat for mpg123 and now Slackware
> supports a pure alsa install in extra. It would really mean a lot to me
> if this was applied to qt5 too so I that I didn't constantly have to
> edit the SlackBuild every time I update or rebuild qt5. Something which
> I routinely forget to do until the build fails...
>
> Can this be done? I've attached the patch to this e-mail.
>
> Thanks,
> Hunter

I'm sorry Hunter, but if these kind of patches are to be applied is up
to the maintainers.
maybe if Larry hasn't answered yet is because he's not gonna apply it,
but he has the last call on his own scripts.
consider also that we assume for our scripts a full and clean
installation of the latest Slackware stable, and such platform contain
pulseaudio, we don't officially support pure alsa installations.

Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/