Re: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?
On 8/10/15, Thomas Szteliga t...@websafe.pl wrote: SlackBuild templates (and scripts) contain this line: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild but what if a SlackBuild script requires patches applied during its execution. Shouldn't they be copied to $PKG/usr/doc/$PRGNAM-$VERSION/ as well? For example, `arj` http://slackbuilds.org/repository/14.1/system/arj/ requires a lot of patches http://slackbuilds.org/slackbuilds/14.1/system/arj/patches/ but the SlackBuild script http://slackbuilds.org/slackbuilds/14.1/system/arj/arj.SlackBuild still contains only: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild leaving the patches out. I've noticed this as well. Does anyone find it helpful that the script is installed in /usr/doc? Maybe we can omit it instead? -Kyle ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?
I've noticed this as well. Does anyone find it helpful that the script is installed in /usr/doc? Maybe we can omit it instead? -Kyle Is anyone really that strapped for disk space that we need to be concerned? If the rare user is that concerned, surely they can write a script to clean out things like this. I like having the build script there, and wouldn't mind the patches being included also. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?
Hi, On 11/08/2015 05:13, Thomas Szteliga wrote: SlackBuild templates (and scripts) contain this line: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild but what if a SlackBuild script requires patches applied during its execution. Shouldn't they be copied to $PKG/usr/doc/$PRGNAM-$VERSION/ as well? For example, `arj` http://slackbuilds.org/repository/14.1/system/arj/ requires a lot of patches http://slackbuilds.org/slackbuilds/14.1/system/arj/patches/ but the SlackBuild script http://slackbuilds.org/slackbuilds/14.1/system/arj/arj.SlackBuild still contains only: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild leaving the patches out. Well, it depends. In the aforementioned case, the patches comes for Debian that distributes them in a tarball found e.g. here for sid https://packages.debian.org/sid/arj In this case the Debian packaging tarball that includes the patches is: http://http.debian.net/debian/pool/main/a/arj/arj_3.10.22-14.debian.tar.xz IMHO including the patches in the SBo tarball, as done for arj, has the inconvennience that we don't know from which Debian packaging tarball (for sid, sqeeze, wheezy,stretch... ?) they come from. I didn't check but maybe the patches differ. For that reason in such a case tend to provide the link to the Debian packaging tarball as a source file unpacked by the SlackBuild, instead of including the patches in the SBo tarball. That's what I have for 'bogl', 'bidiv' or 'newt, not (yet) submitted but available here: http://slint.fr/packages/extra/bogl/build/ http://slint.fr/packages/extra/bidiv/build/ http://slint.fr/packages/extra/newt/build/ For instance: for i in `cat ../debian/patches/series`; do cat ../debian/patches/$i | patch -p1 --verbose done I think that makes the maintenance easier: _ We know from which Debian packaging tarball come the patches _ possibly some of them only are applied, but then we know which are left over. But there are other cases. For Bicon: http://slackbuilds.org/repository/14.1/system/bicon/ the source are on git and I cherry picked a patch from its commit and included it in the SBo tarball. In this case I agree that I could (should?) have provided it in $PKG/usr/doc/$PRGNAM-$VERSION/ possibly in a subdirectory $PKG/usr/doc/$PRGNAM-$VERSION/patches Cheers, Didier PS an attentive reader could notice that newt is already available @http://slackbuids.org. But it is built from the sources hosted @Fedora, that left over a patch allowing 'whiptail to properly display bi-directional text. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64
This was also an issue with libgdiplus in the config file in earlier
versions of mono. The issue seems to now be with MonoPosixHelper library.
I'm providing a slightly updated patch to fix the /usr/lib issue.
Thanks,
--Larry
On Mon, Aug 10, 2015 at 4:14 AM, Thomas Szteliga t...@websafe.pl wrote:
On 08/10/2015 06:07 AM, Christoph Willing wrote:
That is not an appropriate patch; it is completely 64bit-centric, just
as the config in the source code is completely 32bit-centric.
Sorry for that, this patch wasn't meant to be a patch for
the slackbuild package, just for visualisation of changes I've
made that allowed me to run KeePass. Sorry for misleading.
--
Best regards,
Thomas Szteliga
https://github.com/websafe/
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
diff -Naur mono-3.10.0.orig/data/config.in mono-3.10.0/data/config.in
--- mono-3.10.0.orig/data/config.in 2014-10-04 09:27:43.0 +
+++ mono-3.10.0/data/config.in 2015-08-09 14:47:00.208372631 +
@@ -10,7 +10,7 @@
dllmap dll=i:odbc32.dll target=libiodbc.dylib os=osx/
dllmap dll=oci target=libclntsh@libsuffix@ os=!windows/
dllmap dll=db2cli target=libdb2_36@libsuffix@ os=!windows/
- dllmap dll=MonoPosixHelper target=@prefix@/lib/libMonoPosixHelper@libsuffix@ os=!windows /
+ dllmap dll=MonoPosixHelper target=@libdir@/libMonoPosixHelper@libsuffix@ os=!windows /
dllmap dll=i:msvcrt target=@LIBC@ os=!windows/
dllmap dll=i:msvcrt.dll target=@LIBC@ os=!windows/
dllmap dll=sqlite target=@SQLITE@ os=!windows/
--- mono.SlackBuild.orig 2015-08-09 08:46:59.094525671 -0700
+++ mono.SlackBuild 2015-08-09 07:48:21.697376096 -0700
@@ -50,7 +50,9 @@
\( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
-# Fix libgdiplus library path
+# Fix library path in config file
+patch -p1 $CWD/config.patch
+
CFLAGS=$SLKCFLAGS \
CXXFLAGS=$SLKCFLAGS \
./configure \
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Building an older version of VirtualBox
On 8/10/15, JCA 1.41...@gmail.com wrote: I am working in a project which assumes the presence of VirtualBox 4.3.10 - it has to be exactly that version. The current Slackbuilds repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball for 4.3.24, just changing the version number before launching the compilation. However, this fails for the Slackbuilds script attempts to patch the VirtualBox source code - which it assumes to be 4.3.24, not 4.3.10. Rather than attempting to hack this code, I think that the easiest alternative is to try and get the virtualbox.tar.gz tarball that Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in this forum where I can download this tarball from? http://slackbuilds.org/cgit/slackbuilds/log/?qt=grepq=virtualbox Looks like 4.3.10 is on that list. -- --- ryanpcmcquen.com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Building an older version of VirtualBox
On Mon, Aug 10, 2015 at 2:51 PM, Ryan P.C. McQuen rya...@linux.com wrote: On 8/10/15, JCA 1.41...@gmail.com wrote: I am working in a project which assumes the presence of VirtualBox 4.3.10 - it has to be exactly that version. The current Slackbuilds repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball for 4.3.24, just changing the version number before launching the compilation. However, this fails for the Slackbuilds script attempts to patch the VirtualBox source code - which it assumes to be 4.3.24, not 4.3.10. Rather than attempting to hack this code, I think that the easiest alternative is to try and get the virtualbox.tar.gz tarball that Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in this forum where I can download this tarball from? http://slackbuilds.org/cgit/slackbuilds/log/?qt=grepq=virtualbox Looks like 4.3.10 is on that list. -- --- ryanpcmcquen.com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ Much appreciated. I actually downloaded the Slackbuilds tag corresponding to 05/14/2014, which seems to be the one when the VirtualBox 4.3.10 update was picked up. I am sure there must be a more intelligent way of doing it, but this should work for me. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Building an older version of VirtualBox
Much appreciated. I actually downloaded the Slackbuilds tag corresponding to 05/14/2014, which seems to be the one when the VirtualBox 4.3.10 update was picked up. I am sure there must be a more intelligent way of doing it, but this should work for me. If you have the git repo cloned, you can use `git checkout`. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] tornado requires python-certifi
Hi I built the mopidy packagewith all its dependencies, but when I ran I got the following message: pkg_resources.DistributionNotFound: The 'certifi' distribution was not found and is required by tornado Installing the package python-certifi mopidy works fine. Now, I guess python-certifi must be added to the list of dependencies of tornado slackBuild -- Dhaby Xiloj ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?
SlackBuild templates (and scripts) contain this line: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild but what if a SlackBuild script requires patches applied during its execution. Shouldn't they be copied to $PKG/usr/doc/$PRGNAM-$VERSION/ as well? For example, `arj` http://slackbuilds.org/repository/14.1/system/arj/ requires a lot of patches http://slackbuilds.org/slackbuilds/14.1/system/arj/patches/ but the SlackBuild script http://slackbuilds.org/slackbuilds/14.1/system/arj/arj.SlackBuild still contains only: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild leaving the patches out. -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Building an older version of VirtualBox
I am working in a project which assumes the presence of VirtualBox 4.3.10 - it has to be exactly that version. The current Slackbuilds repository builds 4.3.24. I tried using the virtualbox.tar.gz tarball for 4.3.24, just changing the version number before launching the compilation. However, this fails for the Slackbuilds script attempts to patch the VirtualBox source code - which it assumes to be 4.3.24, not 4.3.10. Rather than attempting to hack this code, I think that the easiest alternative is to try and get the virtualbox.tar.gz tarball that Slackbuilds used to build VritualBox 4.3.10 in its day. Anybody in this forum where I can download this tarball from? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64
On 08/10/2015 06:07 AM, Christoph Willing wrote: That is not an appropriate patch; it is completely 64bit-centric, just as the config in the source code is completely 32bit-centric. Sorry for that, this patch wasn't meant to be a patch for the slackbuild package, just for visualisation of changes I've made that allowed me to run KeePass. Sorry for misleading. -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
