I'm going to throw in a paltry suggestion to use sbotools, which captures
the spirit of BSD's ports. (We don't need no stinkin' ncurses interface)
But if you want to take others' suggestion of not using any tools that is
also fine.

On Mon, October 12, 2015 16:07, [email protected]
wrote:
> Send SlackBuilds-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SlackBuilds-users digest..."
>
>
> Today's Topics:
>
>
> 1. Re: Pulseaudio (Citizen X)
> 2. Re: Pulseaudio (Ryan P.C. McQuen)
> 3. Re: Pulseaudio (Citizen X)
> 4. Re: Pulseaudio (Citizen X)
> 5. Re: Pulseaudio (Didier Spaier)
> 6. Building Stellarium from the 14.1 repositories (EM Uhill)
>
>
>
> ----------------------------------------------------------------------
>
>
> Message: 1
> Date: Mon, 12 Oct 2015 10:45:01 -0400
> From: Citizen X <[email protected]>
> To: "SlackBuilds.org Users List" <[email protected]>
> Subject: Re: [Slackbuilds-users] Pulseaudio
> Message-ID:
> <cadcvwq1jyujz7nt+niybj3vfbjycp64yd47tlvwsaxwyfia...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> I just noticed that the slackbuild, which I tried to install with
> slapt-src ends up with 6.0 source in it's directory and the build is for
> 7.0
>
>
> On Sun, Oct 11, 2015 at 1:34 PM, B Watson <[email protected]> wrote:
>
>
>> On 10/11/15, Christoph Willing <[email protected]> wrote:
>>
>>> Which pulseaudio version? The most recent 7.0 uses the
>>> /usr/share/bash-completion/completions directory, as does the
>>> bash-completion package itself (not /etc/bash_completion.d).
>>
>> Ah, my bad, I was looking at pulse 6.0, had forgot to 'git pull'.
>>
>>
>>> Even better - there is a --with-bash-completion-dir=DIR option
>>>
>>
>>> That's what will go into the amended SlackBuild for the next round of
>>>
>> updates
>>
>> That sounds like the right answer.
>> _______________________________________________
>> SlackBuilds-users mailing list
>> [email protected]
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/201
> 51012/79f4dd58/attachment-0001.html>
>
>
> ------------------------------
>
>
> Message: 2
> Date: Mon, 12 Oct 2015 07:47:29 -0700
> From: "Ryan P.C. McQuen" <[email protected]>
> To: "SlackBuilds.org Users List" <[email protected]>
> Subject: Re: [Slackbuilds-users] Pulseaudio
> Message-ID:
> <caacyf-qgachp_6jbaz-q+1ph_cgusmt8qevyikcq86cbtdk...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
>
> On Mon, Oct 12, 2015 at 7:45 AM, Citizen X <[email protected]>
> wrote:
>
>> I just noticed that the slackbuild, which I tried to install with
>> slapt-src ends up with 6.0 source in it's directory and the build is for
>> 7.0
>>
>
>
>
> Never trust automatic tools. The .info clearly points to the 7.0 tarball:
>
>
> http://slackbuilds.org/slackbuilds/14.1/audio/pulseaudio/pulseaudio.info
>
>
> http://freedesktop.org/software/pulseaudio/releases/pulseaudio-7.0.tar.xz
>
>
> You probably need to do slapt-src's equivalent of `sbopkg -r`.
>
>
>
>
> --
> -Ryan
> [ryanpcmcquen.org]
>
>
>
> ------------------------------
>
>
> Message: 3
> Date: Mon, 12 Oct 2015 11:01:26 -0400
> From: Citizen X <[email protected]>
> To: "SlackBuilds.org Users List" <[email protected]>
> Subject: Re: [Slackbuilds-users] Pulseaudio
> Message-ID:
> <cadcvwq1h4pq2rgoms9befgyhy-e5xcrfsiflvftejrjbnba...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> Noticed these 2 lines
> sed -i -e '/@PA_BINARY@/ imkdir -p \$HOME/.config/pulse' src/daemon/
> start-pulseaudio-x11.in echo "X-MATE-Autostart-Phase=Initialization"
> >>src/daemon/ pulseaudio.desktop.in
>
> Shouldn't MATE be checked for and then if installed then do that?
>
>
> Can it apply to Xfce as well?
>
>
> On Mon, Oct 12, 2015 at 10:45 AM, Citizen X <[email protected]>
> wrote:
>
>
>> I just noticed that the slackbuild, which I tried to install with
>> slapt-src ends up with 6.0 source in it's directory and the build is for
>> 7.0
>>
>>
>> On Sun, Oct 11, 2015 at 1:34 PM, B Watson <[email protected]> wrote:
>>
>>
>>> On 10/11/15, Christoph Willing <[email protected]> wrote:
>>>
>>>> Which pulseaudio version? The most recent 7.0 uses the
>>>> /usr/share/bash-completion/completions directory, as does the
>>>> bash-completion package itself (not /etc/bash_completion.d).
>>>
>>> Ah, my bad, I was looking at pulse 6.0, had forgot to 'git pull'.
>>>
>>>
>>>> Even better - there is a --with-bash-completion-dir=DIR option
>>>>
>>>
>>>> That's what will go into the amended SlackBuild for the next round
>>>> of
>>> updates
>>>
>>> That sounds like the right answer.
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> [email protected]
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - http://slackbuilds.org/faq/
>>>
>>>
>>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/201
> 51012/61622ec3/attachment-0001.html>
>
>
> ------------------------------
>
>
> Message: 4
> Date: Mon, 12 Oct 2015 15:31:59 -0400
> From: Citizen X <[email protected]>
> To: "SlackBuilds.org Users List" <[email protected]>
> Subject: Re: [Slackbuilds-users] Pulseaudio
> Message-ID:
> <cadcvwq3tpw1evv_fgu4vxrtnfjhua+ksbxlsndyn7zcct_y...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> Been considering switching to sbopkg because I hear good things. I know
> that the info file is 7.0 & points at 7.0 and the script says 7.0 but when
>  fetching from slackbuilds.org it's grabs the 6.0 source. grabbed it with
>  wget but I am having weird issues now. Looking like I need to do a fresh
>  install again. =(
>
> On Mon, Oct 12, 2015 at 10:47 AM, Ryan P.C. McQuen <[email protected]>
> wrote:
>
>
>> On Mon, Oct 12, 2015 at 7:45 AM, Citizen X <[email protected]>
>> wrote:
>>
>>> I just noticed that the slackbuild, which I tried to install with
>>>
>> slapt-src
>>> ends up with 6.0 source in it's directory and the build is for 7.0
>>
>>
>>
>> Never trust automatic tools. The .info clearly points to the 7.0
>> tarball:
>>
>>
>> http://slackbuilds.org/slackbuilds/14.1/audio/pulseaudio/pulseaudio.inf
>> o
>>
>> http://freedesktop.org/software/pulseaudio/releases/pulseaudio-7.0.tar.
>> xz
>>
>> You probably need to do slapt-src's equivalent of `sbopkg -r`.
>>
>>
>>
>>
>> --
>> -Ryan
>> [ryanpcmcquen.org]
>> _______________________________________________
>> SlackBuilds-users mailing list
>> [email protected]
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/201
> 51012/09fb0eba/attachment-0001.html>
>
>
> ------------------------------
>
>
> Message: 5
> Date: Mon, 12 Oct 2015 22:04:34 +0200
> From: Didier Spaier <[email protected]>
> To: [email protected]
> Subject: Re: [Slackbuilds-users] Pulseaudio
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
>
>
> On 12/10/2015 21:31, Citizen X wrote:
>
>> Been considering switching to sbopkg because I hear good things. I know
>>  that the info file is 7.0 & points at 7.0 and the script says 7.0 but
>> when fetching from slackbuilds.org it's grabs the 6.0 source. grabbed it
>> with wget but I am having weird issues now. Looking like I need to do a
>> fresh install again. =(
>
> So as Ryan said that's not a problem with slackuilds.org but with the
> tool you use, or maybe the ay you use it.
>
> For instance If you use sbopkg, never forget to sync the repository
> before making an installation or update
>
> Cheers,
> Didier
>
>
>
> ------------------------------
>
>
> Message: 6
> Date: Mon, 12 Oct 2015 13:07:58 -0700
> From: EM Uhill <[email protected]>
> To: [email protected]
> Subject: [Slackbuilds-users] Building Stellarium from the 14.1
> repositories Message-ID:
> <cal-oaoqzdeq7cayy7g945epkdqytdokqa9pn2ds61atmvcl...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
>
> I emailed this to the Stellarium maintainer, Alan Alberghini, without any
>  reply back, so I am posting it here on the mailing list so the Slackware
>  community can benefit from my experiences with building and installing
> Stellarium with qt-5.5 installed as found in the Slack Builds 14.1
> repository.
>
> Hi there. I tried to install Stellarium 0.13.2 via your Slack Build
> script only to find out it won't compile against qt-5.5. This is the only
> version of qt on Slack builds for Slackware 14.1. Stellarium's website
> shows that Stellarium 0.13.2 needs qt-5.2 to build. I haven't tried it,
> but I presume that the qt-5.5 SlackBuild script would compile the 5.2
> version of qt just fine. However that takes 12 hours to build on my duo
> core machine. Since I already had qt-5.5 built, I modified your SlackBuild
> script to build Stellarium 0.13.3 and included a patch from the Gentoo
> website so it would build against qt-5.5. The patch will not work with
> Stellarium 0.13.2
> however. After I got it built and installed, I ended up finding out that
> Stellarium 0.13.3 requires Mesa 10.x libraries to function at a decent
> speed. After consulting Stellarium's website, I found out that all
> versions of Stellarium after 0.12.4 require Mesa 10.x libs to be installed
> including Stellarium 0.12.6. The Stellarium project recommends upgrading
> to one of the Mesa 10.x libs to run any version of Stellarium after 0.12.4
> or to use 0.12.4 for the Mesa 9.x libs.  As a result I have used your
> original SlackBuild script to build and install Stellarium 0.12.4 and it
> works just fine.  You'll probably want to update your Stellarium
> Slackbuild entry to
> use Stellarium 0.13.3 for those who have one of the Mesa 10.x libs
> installed and add another entry for Stellarium 0.12.4 for those who have
> Mesa 9.x libs installed. Attached are two diff patches. One to patch your
>  SlackBuild script to patch and build Stellarium 0.13.3 and the other
> patch is the Gentoo patch that will allow for building against qt-5.5. The
>  changes to your SlackBuild script will only apply Gentoo's qt-5.5 patch
> only if $QT55 is set to 'YES'. I have it set to 'NO' by default just in
> case someone has an earlier version of qt5 installed.
>
> Regards,
>
>
> Eric Underhill
>
>
> The two diff files are below:
>
>
> stellarium.SlackBuild.diff
>
> --- stellarium.SlackBuild     2015-09-24 12:39:19.000000000 -0700
> +++ stellarium-qt55.SlackBuild        2015-09-24 12:44:12.539867926 -0700
> @@ -26,6 +26,9 @@
> VERSION=${VERSION:-0.13.3}
> BUILD=${BUILD:-1}
> TAG=${TAG:-_SBo}
> +# Change to 'YES' if building against qt55 otherwise Stellarium will fail
> to +# build.
> +QT55=${QT55:-NO}
>
>
> if [ -z "$ARCH" ]; then case "$( uname -m )" in @@ -68,6 +71,12 @@
> -o -perm 511 \) -exec chmod 755 {} \; -o \
> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
> -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
> +
> +#If building against qt55 apply patch to fix building against qt55
> +if [ "$QT55" = "YES" ]; then
> +  cp $CWD/$PRGNAM-$VERSION.qt55.patch $TMP/$PRGNAM-$VERSION
> +  patch p1 < $PRGNAM-$VERSION.qt55.patch
> +fi
>
>
> mkdir build && cd build cmake -DCMAKE_INSTALL_PREFIX=/usr \
>
>
>
> stellarium-0.13.3-qt55.patch
>
> diff -ur -x CMakeFiles -x Makefile -x 'CMake*'
> stellarium-0.13.2/work/stellarium-0.13.3/src/CLIProcessor.hpp
> stellarium-0.13.3-new/work/stellarium-0.13.3/src/CLIProcessor.hpp ---
> src/CLIProcessor.hpp       2015-03-08 12:41:55.000000000 +0100 +++
> src/CLIProcessor.hpp   2015-07-12 13:29:36.059179087 +0200 @@ -21,6 +21,7
> @@
> #define CLIPROCESSOR_HPP
>
>
> #include <QStringList>
> +#include <QVariant>
>
>
> class QSettings;
>
> diff -ur -x CMakeFiles -x Makefile -x 'CMake*'
> stellarium-0.13.2/work/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp
> stellarium-0.13.3-new/work/stellarium-0.13.3/src/core/StelSkyCultureMgr.h
> pp --- src/core/StelSkyCultureMgr.hpp     2015-03-08 12:41:55.000000000
> +0100
> +++ src/core/StelSkyCultureMgr.hpp 2015-07-12 13:28:32.589064791 +0200
> @@ -23,6 +23,7 @@
> #include <QMap>
> #include <QString>
> #include <QStringList>
> +#include <QObject>
>
>
> //! @class StelSkyCulture
> //! Store basic info about a sky culture for stellarium.
>
>
> diff -ur -x CMakeFiles -x Makefile -x 'CMake*'
> stellarium-0.13.2/work/stellarium-0.13.3/src/CLIProcessor.hpp
> stellarium-0.13.3-new/work/stellarium-0.13.3/src/CLIProcessor.hpp ---
> src/core/StelLocationMgr.cpp    2015-02-25 12:30:31 +0000 +++
> src/core/StelLocationMgr.cpp    2015-03-03 14:34:38 +0000 --------------
> next part -------------- An HTML attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/201
> 51012/36ecbc85/attachment.html>
>
>
> ------------------------------
>
>
> Subject: Digest Footer
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> [email protected]
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>
>
> ------------------------------
>
>
> End of SlackBuilds-users Digest, Vol 114, Issue 11
> **************************************************
>
>


Steve Wood
[email protected]
203.841.9792
xmpp: [email protected]

_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Reply via email to