Hi,
I suggest setting up or updating a separate repository of runit scripts,
as I suspect that only a handful of us use runit.
This is my modest contribution:
https://gitlab.com/chrisabela/runit_scripts_for_slackware. Feel free to
take the lead, fork, follow, copy, contribute or whatever.
See here:
https://www.slackwiki.com/Packages
https://www.slackwiki.com/Building_A_Package
http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
http://docs.slackware.com/howtos:find_packages_with_filenames
Hi All,
I am not in a position to maintain the davfs SalckBuild any longer. Please
let us know if anyone is interested in taking over.
Chris Abela
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org
c/mounts
>
> Il mar 2 giu 2020, 17:35 Chris Abela ha scritto:
>
>> No Matteo,
>>
>> $ ls -ld /tmp
>> drwxrwxrwt 12 root root 102400 Jun 2 17:29 /tmp/
>>
>> I notice that I missed some dependencies as my queue files were outdated.
>> My bu
, 2020 at 5:35 PM Chris Abela wrote:
> No Matteo,
>
> $ ls -ld /tmp
> drwxrwxrwt 12 root root 102400 Jun 2 17:29 /tmp/
>
> I notice that I missed some dependencies as my queue files were outdated.
> My building machine is very slow, so please stand-by until I update you.
>
&
ard...@gmail.com> wrote:
> Seeing that "permissione denied" makes me think that you are trying to
> build it with a /tmp filesystem mounted with a "noexec" option...
> Is that the case?
> If It is, try to export a different TMP for building just calibro.
>
&
I have installed updated packages of all the dependencies but clibre will
still not build:
### Building extension podofo ###
### Building extension pictureflow ###
Traceback (most recent call last):
File "setup.py", line 121, in
sys.exit(main())
File "setup.py", line
That works!
Thank you
Chris
On Thu, 16 Jan 2020, 19:52 Franzen, wrote:
> On 2020-01-16 18:49, Chris Abela wrote:
> > Since ftgl-2.4.0 was updated, projectM will not build:
> >
> > -- Generating done
> > -- Build files have been written to:
> > /tmp/SBo/pro
Since ftgl-2.4.0 was updated, projectM will not build:
-- Generating done
-- Build files have been written to:
/tmp/SBo/projectM-complete-2.1.0-Source/build
Scanning dependencies of target Renderer
[ 1%] Building CXX object
src/libprojectM/Renderer/CMakeFiles/Renderer.dir/FBO.cpp.o
[ 2%]
Greeting Everyone,
wireshark will not build
Chris
Scanning dependencies of target capinfos
[ 92%] Building C object CMakeFiles/capinfos.dir/capinfos.c.o
[ 92%] Linking C executable run/capinfos
[ 92%] Built target capinfos
Scanning dependencies of target sharkd
[ 92%] Building C object
For my $HOME directory, I use nextcloud. It requires php7 and it is
overkill for my purpose but it works.
On Tue, 10 Sep 2019, 21:38 Rich Shepard, wrote:
> On Tue, 10 Sep 2019, Greg' Ar Tourter wrote:
>
> > One I have used in the past is backuppc (
> > https://backuppc.github.io/backuppc/). It
Try
sbopkg -R -k -i "queue1.sqf queue2.sqf "
On Sun, 4 Aug 2019, 00:05 Rich Shepard, wrote:
> On Sat, 3 Aug 2019, Chris Abela wrote:
>
> > I confess that I have not understood your query well but I will attempt
> to
> > reply.
>
> Chris,
>
>
Happy Birthday SBo,
I have been on Slackware for more than 11 years and I did occasionally veer
out to other distributions, only to fire up a Slack VM to play with my
slackbuilds again.
Your successful open contributions model has enhanced the Slackware
experience tremendously.
Chris
On Thu,
Hi,
Indeed it is. Thank You for your reply.
Chris
On Tue, 7 May 2019, 22:52 Markus Rinne, wrote:
> Hello,
>
> On Tue, May 07, 2019 at 08:29:07AM +0200, Chris Abela wrote:
> > I used to have the SBo chrome, but now I installed the package from
> > alienbob's r
Correction; its "chromium" not "chrome"
On Tue, May 7, 2019 at 8:29 AM Chris Abela wrote:
> I used to have the SBo chrome, but now I installed the package from
> alienbob's repo and removed ninja.
>
> From ninja.slackBuild:
>
> D
I used to have the SBo chrome, but now I installed the package from
alienbob's repo and removed ninja.
>From ninja.slackBuild:
DESTDIR=$PKG ninja -C build all install
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
Thank You.
Next time, I should check the git repo before claiming any bug fix.
Cheers,
Chris
On Thu, Mar 28, 2019 at 9:42 AM Christoph Willing
wrote:
> On 28/3/19 6:18 pm, Chris Abela wrote:
> > On my 14.2 systems, vlc does not build:
> >
> > access
Typo in the title; should read libssh2-1.8.1
On Thu, Mar 28, 2019 at 9:18 AM Chris Abela wrote:
> On my 14.2 systems, vlc does not build:
>
> access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521' undeclared
> (first use in this function)
> knownhost_f
On my 14.2 systems, vlc does not build:
access/sftp.c:319:42: error: 'LIBSSH2_KNOWNHOST_KEY_ECDSA_521' undeclared
(first use in this function)
knownhost_fingerprint_algo = LIBSSH2_KNOWNHOST_KEY_ECDSA_521;
I found a solution here:
Thank You Christoph,
As soon as I find some time, I will try them out.
Chris
On Tue, Mar 26, 2019 at 9:23 AM Christoph Willing
wrote:
> On 26/3/19 4:59 pm, Christoph Willing wrote:
> > On 26/3/19 4:25 pm, Chris Abela wrote:
> >> I am unable to download the sourc
Hi Matteo,
Thank You for the link.
Chris
On Tue, Mar 26, 2019 at 8:05 AM Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:
>
> Il mar 26 mar 2019, 07:26 Chris Abela ha scritto:
>
>> I am unable to download the sources for libopenshot and
>> libopenshot-audi
I am unable to download the sources for libopenshot and libopenshot-audio;
I am getting an HTTP 404 Error. Is anyone willing to provide alternative
links or share the code?
Chris
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
Thank You
On Fri, 8 Mar 2019, 12:04 Christoph Willing,
wrote:
> On 8/3/19 8:09 pm, Chris Abela wrote:
> > python3-Cython built fine against python3-3.6.7 but not against
> > python3-3.7.2
> >
> There's a fix in the ready queue for next SBo update at the weekend. If
&g
python3-Cython built fine against python3-3.6.7 but not against
python3-3.7.2
This is the trace:
running build_ext
cythoning /tmp/SBo/Cython-0.23.4/Cython/Plex/Scanners.py to
/tmp/SBo/Cython-0.23.4/Cython/Plex/Scanners.c
Traceback (most recent call last):
File "setup.py", line 306, in
opera-developer-ffmpeg-codecs depends on opera-developer, while the README
of the latter recommends the former. To a distracted user, this could lead
to a dependency hell.
Chris
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
?
Chris Abela
___
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/
e Slackware a better experience.
Chris Abela
___
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 - htt
Audacity will not build:
make[2]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
make[1]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
unzip: cannot find or open
/var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-*2.2.1*.zip,
qt5-webkit is listed a dependency for nextcloud-client, however this is
only required if qt5 is found.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives -
$ requiredbuilder -i tor
attr
glibc-solibs
libcap
libevent
*libseccomp*
openssl | openssl-solibs
xz
zlib
$ whereis libseccomp
libseccomp: /usr/lib64/libseccomp.la /usr/lib64/libseccomp.so
$ grep usr/lib64/libseccomp /var/log/packages/*
Both tesseract and leptonica (required by tesseract) picked libwebp as a
dependency.
I removed libwebp, rebuilt leptonica and tesseract, reinstalled libwebp
and now ffmpeg is building fine.
Thanks to Arnaud for his hint.
Chris
On 02/11/17 08:59, Chris Abela wrote:
ffmpeg builds fine
ffmpeg builds fine against libwebp-0.5.2, but fails when built against
libwebp-0.6.0:
ffmpeg-3.2.4/tests/tiny_psnr.c
ffmpeg-3.2.4/ffserver.c
ffmpeg-3.2.4/ffmpeg.h
ffmpeg-3.2.4/ffmpeg_dxva2.c
ffmpeg-3.2.4/cmdutils_opencl.c
ffmpeg-3.2.4/COPYING.LGPLv2.1
ffmpeg-3.2.4/ffmpeg_vaapi.c
1. On my machines, ffmpeg built against the previous version (à la
wireshark). Removing it before building it again solved missing
libraries issues.
2. On my second run, ffmpeg complained on missing chromaprint, despite
that I had it. Disabling it solved this problem
3. On third time, I got
On 06/02/17 11:21, Chris Abela wrote:
On 04/02/17 01:55, Willy Sudiarto Raharjo wrote:
Hi,
For letsencrypt users, you may want to install python-future since it's
now required for python-parsedatetime and letsencrypt will complaint
without it.
I missed this dep in this public update
On 04/02/17 01:55, Willy Sudiarto Raharjo wrote:
Hi,
For letsencrypt users, you may want to install python-future since it's
now required for python-parsedatetime and letsencrypt will complaint
without it.
I missed this dep in this public update, but it has been merged in my
branch and will
I confirm that after building python from source, chromium builds fine.
On 10 Jan 2017 16:58, "Matteo Bernardini" <matteo.bernard...@gmail.com>
wrote:
> 2017-01-10 15:06 GMT+01:00 Chris Abela <kristo...@gmail.com>:
> > I suspect that the python upgrade of the
/usr/bin/dcadec is found in two SBo packages; in dcadec a kodi dependency
and libdca, a vlc dependency:
$ sudo /sbin/installpkg --warn dcadec-0.2.0-x86_64-1_SBo.txz
/usr/bin/dcadec
$ grep usr/bin/dcadec /var/log/packages/*
/var/log/packages/libdca-0.0.5-x86_64-1_SBo:usr/bin/dcadec
I use fakeroot extensively when building my slackbuilds manually. As far as
I remember only qemu refused to build once.
On Sun, 30 Oct 2016 14:28 Andrzej Telszewski, wrote:
> On 30/10/16 12:02, Franzen wrote:
> > On 2016-10-30 11:08, Andrzej Telszewski wrote:
> >> Hi,
>
I confirm that it built fine on a newer machine. I also agree that it looks
like a localised hardware issue. I will take it from here.
Thank You
Chris
On Sun, 23 Oct 2016 02:44 King Beowulf, <kingbeow...@gmail.com> wrote:
> On 10/20/2016 06:55 AM, Chris Abela wrote:
> > I have
Mine probably built against the stock qt4. It works fine.
On 20 Oct 2016 16:44, "Willy Sudiarto Raharjo"
wrote:
> > I successfully built wireshark without qt5. Perhaps we consider removing
> it
> > from the REQUIRED list.
>
> No, it's still required for the new user
I have new and default x86_64 Slackware 14.2 installation. qt5 does not
build. The last 50 lines of my build logs may be found here:
http://pastebin.com/Y4EGGMYB
I do not need qt5 but I thought that you would want to know.
Chris
___
SlackBuilds-users
I successfully built wireshark without qt5. Perhaps we consider removing it
from the REQUIRED list.
Chris
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives -
haven't ruled out going back to slack... I just need a wee lie down first..
:)
pretty freaky having 2 servers on one box ;)
On 8/17/2014 2:26 AM, Chris Abela wrote:
I suppose that you are referring to the INFO file. The required field is
for dependencies.
Chris Abela
On 17 Aug 2014 01
Reading http://slackbuilds.org/slackbuilds/14.1/system/xen/dom0/README.dom0
I understand that you need a custom kernel for dom0.
Chris
On 16 Aug 2014 16:51, Paul McCormack islandmar...@gmail.com wrote:
I'm not sure that my first post made it through so the humour may be
lost but here goes.
I suppose that you are referring to the INFO file. The required field is
for dependencies.
Chris Abela
On 17 Aug 2014 01:07, Paul McCormack islandmar...@gmail.com wrote:
I thought that was optional and if it it is required then shouldn't the
slackbuild reflect that?
On 16 Aug 2014 18:16
network/etherape
network/gq
network/ip2location-c
network/ipv6calc
network/wput
network/xinetd
office/ganttproject
system/burp
system/cronie
system/davfs2
system/dump
system/vlock
Chris Abela
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
chris.ab...@maltats.com is my professional e-mail - used in some original
submissions
kristo...@gmail.com is my personal e-mail - I am am migrating to this one
I am updating my email information only when updates are required as I am
still able to respond to both accounts.
Chris
On Mon, Nov
I am not maintaining openproj anymore. I am not using it as it has been
abandoned since 2008 and now it does not compile on my Slack64-current.
I use ProjectLibre instead - it is similar but better maintained.
___
SlackBuilds-users mailing list
The HOMEPAGE entry of libnova has a double http:// prefix:
$ grep HOMEPAGE /var/lib/sbopkg/SBo/14.0/libraries/libnova/libnova.info
HOMEPAGE=http://http://libnova.sourceforge.net/;
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
that
further information is contained therein.
Information related to the execution of the application that is built by
the SlackBuild are normally included in the README.* file.
Chris
On Wed, Apr 24, 2013 at 11:00 PM, Marc Vertes marc.ver...@sigfox.comwrote:
Chris Abela wrote:
On 04/24
On 04/24/2013 07:55 PM, Marc Vertes wrote:
Hello,
I found that the following dependencies are necessary to build zyGrib, but are
not mentioned:
libnova, proj and qwt.
Regards,
--
Marc
___
SlackBuilds-users mailing list
I think that we would be hard pressed to find many default Slackware
installations in the wild.
My choice was to write a small /etc/profile.d/local.sh (with executable
permissions of course). Then I use sbopkg most of the time.
#!/bin/sh
# SBo parameters
export PKGTYPE=txz
export
The URL shown for the source code on the website is currently:
http://ponce.cc/slackware/sources/repo/recode-3.6.tar.gz works but the
one shown in the INFO file is still unavailable.
I apologize if this is in hand but I am frequently being notified by
users and I think that I am duty bound to let
As I do not follow -current my Slackbuilds could not be updated for a
long time, but I managed to catch up and the following is the status
of the SlackBuilds that are currently under my maintenance. Naturally
I do this on a best effort basis but if you disagree with anything
here or you would like
On Thu, Nov 15, 2012 at 6:01 AM, Robby Workman rwork...@slackbuilds.org wrote:
:
Off is the general direction in which you can fuck.
In our internal discussions about adding REQUIRES, one of the most
frequent concerns was feature creep, i.e. if we do that, then
people are going to want
I am trying to install ffmpeg with all optional dependencies but I was
faced with an impossible task:
ffmpeg has frei0r as an optional dependency
frei0r has opencv as an optional dependency
opencv has ffmpeg as an optional dependency
Do you have an idea how I can get out of this loop or do I
As a starting point build opencv without the ffmpeg depndency, then build all
the other packages. If you have done that built another package of opencv
with the ffmpeg dependency.
I therefore conclude that the ffmpeg option for opencv will not have
any contribution to the final ffmpeg build.
I have been notified by a user that the the vlock source code link is
dead. On checking I found that even the homepage is gone. I sent an
e-mail to the upstream maintainer on his plans, but I did not get any
response. As vlock is a security application I would like this mailing
list to know
On 08/13/2012 06:13 PM, Kent Fritz wrote:
Moved here?
http://freecode.com/projects/vlock
I am not familiar with freecode.com but I see that the maintainer is not
the same one who signed the README and the link to source code is the
original (dead) one. As far as I can judge, the freecode
While trying to reach him the source for the latest version is readily
available in both the OpenSuse and archives and from PacketStorm.
I also have a copy I can post if it's of help. Best to get it from the
maintainer but ports in a storm as they say.
I am not too happy to be involved in
Hi Niki,
Yes I had inherited the maintenance of this SlackBuild from you as I
wanted a slight modification to build recode on Slack 13.0.
I have just submitted an update for recode.info:
DOWNLOAD=http://slackermedia.info/slackbuilds/recode-3.6.tar.gz
(thanks to klaatu)
Presently I am looking
For those that do
not, I hope that they would forgive my naivety.
2011 is an exceptional year and will leave some indelible memories - both
good and bad. Nevertheless, may 2012 be a better year for all of us.
Chris Abela
___
SlackBuilds-users mailing list
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
[mailto:slackbuilds-users-boun...@slackbuilds.org] On Behalf Of korgman
Sent: 25 November 2011 00:21
To: SlackBuilds mailing-list
Subject: [Slackbuilds-users] youtube-dl - Maintainer not respond
Hello there
The
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
[mailto:slackbuilds-users-boun...@slackbuilds.org] On Behalf Of Niels Horn
Sent: 22 October 2011 15:24
To: SlackBuilds.org Users List
Subject: [Slackbuilds-users] Updates - 20111022.1
Sat Oct 22 12:23:02 UTC 2011
Did you run the command as root (or at least with sudo)? Normal users
can't use setcap.
If you still get operation not permitted when running setcap as root,
it's possible you're using a filesystem that doesn't support POSIX
capabilities. However, all the filesystem types Slackware normally
2011/6/16 Chris ABELA chris.ab...@maltats.com:
3. Upgrade them but do not bother with any other packages even if they
were
I got for that all the time.
--
Ozan, BSc, BEng
Well, if you upgrade a library, you might need to rebuild the packages
that depend on it.
This all depends on how
I noticed that there were some updates on some SBo packages I had already
installed on my new Slackware 13.37 installation. Given some possible
options that come to my mind, what would you consider as the best practice?
1. Ignore them unless there are some security issues.
2. Upgrade them and
Will someone from the Admins please remove my submission for loic. I made
some significant enhancements I would like to include before your review.
Unlike other submissions I had made before, I did not receive the mail with
instructions on how to do this.
Chris
What procedure is taken in order to avoid this nightmare?
Because, knowing SlackBuild.org has a very good reputation and its
software works flawlessly most of the times, I asume you have some
method to prevent Niel and his friends from taking over Slackware
Universe.
From:
I consider this from the point of liability.
If you can employ an auditor to mitigate your liability, then just do it.
If you do not have any liabilities then you have no problems.
If you have liability and you do not afford an auditor then you are in the
wrong business.
Chris
Powered by
I didn't opt for the rebuild of xulrunner, because when I checked, my
package was tagged 'alien', and I can't for the life of me remember why
I would have used the AlienBOB version (perhaps it had something to do
with my 'custom', offshore versions of ffmpeg, mplayer, etc. ;) ).
The
.
-- Hermann Goering, Nazi and war criminal, 1883-1946
The community does not deserve this. The Nazi reference is unwarranted and
insults the memory of victims of dictatorship.
Chris Abela
Ing. Christopher Abela
B. Elec. Eng. (Hons) M.Sc. Eng (Malta)
Senior Head Technical Services
Malta
Chris -
It's just a quote in an email signature, it has nothing to do with the
present conversation.
Much like the giant confidentiality notification on your outgoing email, or
Willy's links in his.
--JK
higuita and All,
I did not understand that it was a signature, thus I
Out of curiosity, what would be the potential downsides to bumping the
build numbers?
We write SlackBuilds so build numbers should reflect SlackBuilds. It is up
to the users to compile, package and install on their machines.
___
SlackBuilds-users
Dear gang,
I just did a fresh Slackware installation; I only installed Fluxbox,
because it was intended to be a platform for building Xfce 4.8.
However, I rediscovered my appreciation of Fluxbox... so that is where
I will be for a while.
Now, I have come to appreciate having a file manager. As
Dear Geetha,
Someone on
http://www.linuxquestions.org/questions/slackware-14/cant-install-rmagick-ru
by-gem-853918/
has posted a question on Rmagick not working on Slackware. Are you still
maintaining it?
Chris
_
From: slackbuilds-users-boun...@slackbuilds.org
My main motivation for writing and maintaining SlackBuilds is that perennial
fear of the question:
So, what have you ever done for humanity?
Now I have an answer. Probing further is superficial, as far as I am
concerned.
Chris
___
SlackBuilds-users
Probing further is superficial
Apologies for the oxymoron.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives -
Same here with Googleearth on Nvidia.
All you (we) need are both the 64 bit and the 32 bit nvidia drivers.
See: http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib
Caveats
After installing the -compat32 packages, you may have to re-install your
binary Nvidia or Ati video X.Org
AM, Chris Abela wrote:
On the other hand, if you originally only installed the 64bit driver
libraries for your Nvidia/Ati card, it is recommended after installation of
the multilib packages, to re-install the binary driver package. This time,
choose to install the 32bit driver files as well
Packages included in Slackware should not be in SBo. Thus enhances the case
for a PAM SlackBuild. While Pat is/was correct, PAM is usually included in
my Linux Training documentation and so it must have academic interest.
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
If any good soul out there may forward me a copy of this despicable
SlackBuild I will see personally in reporting back why the Slack Police
ought to scan our machines for any trace of Swiss cheese on routine basis.
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
SBo automated dependency resolution already exist:
See:
http://www.mail-archive.com/slackbuilds-users@slackbuilds.org/msg02733.html
Installing gnome packages without sbopkg sqf can be painful.
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
network/avahi: Updated README with gtk-sharp dep.
The README is indeed updated, but
http://slackbuilds.org/repository/13.1/network/avahi/ isn't.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
Hi,
In order to try webdav application, you need a webdav account on a webdav
server. Normally you need certificate/s to log in. I did not find any
functional free webdav servers with which one may test the webdav client,
but I have access to such a server that I use for my application. That is
On my multilib -stable-13.0:
Script started on Fri 14 May 2010 10:14:26 AM CEST
r...@deepthought:~/slackbuilds/vi# / ./t
vi.SlackBuild
ex-050325/ex.spec
ex-050325/regexp.h
ex-050325/libuxre/wcharm.h
ex-050325/libuxre/regex.h
ex-050325/libuxre/regdfa.h
ex-050325/libuxre/re.h
Works here!
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
[mailto:slackbuilds-users-boun...@slackbuilds.org] On Behalf Of Šime Ramov
Sent: 13 May 2010 19:56
To: slackbuilds-users@slackbuilds.org
Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot
While one must appreciate the work involved in the 13.0 to 13.1 update, a
warning on this mail list that the submissions shall be closing would have
been conductive to the combined effort solicited to maintain scripts.
-Original Message-
From: slackbuilds-users-boun...@slackbuilds.org
In order to submit an update for qhull-2010 I had written a patch to be able
to compile it and build it on Slack. I also verified that the Octave build
in the repository could also pick it up.
Yet a few weeks later an updated Octave was submitted, and in order to be
able to compile against
I wanted to build the package for gcompris which is having a dependency of
pysqlite2. I am not able to find the slackbuild for pysqlite2.
Slackware: 12.2
The one for Slack12.1 might work:
http://ftp.slackbuilds.org/repository/12.1/development/pysqlite2/
Hi Sbo's,
The Homepage and Download link for the urlgrabber do seem available any
more.
PRGNAM=urlgrabber
VERSION=3.1.0
HOMEPAGE=http://linux.duke.edu/projects/urlgrabber/;
DOWNLOAD=http://linux.duke.edu/projects/urlgrabber/download/urlgrabber-3.1.
0.tar.gz
DOWNLOAD_x86_64=
HAPPY NEW YEAR TO YOU ALL.
Slackware would be much poorer with slackbuilds.org. Your effort is
appreciated by all the community. I just hope that you enjoy it as well.
Please replace
http://slackbuilds.org/slackbuilds/13.0/system/davfs2/MINI_HOWTO with the
attached. There are a few silly typos
: kristo...@gmail.com
Subject: Re: [Slackbuilds-users] davfs2.SlackBuild
On Tue, 3 Nov 2009 18:07:15 +0100
Chris Abela kristo...@gmail.com wrote:
What shall happen to davfs2.SlackBuild? It is still in the 12.2 and
12.1 repositories and it worked on my Slack64-13.
From the ChangeLog:
...
network
it and resubmitting it. Try emailing the maintainer
and if you don't get a response feel free to submit a build.
Regards
Ash Wiren
On Wed, Nov 4, 2009 at 1:07 AM, Chris Abela kristo...@gmail.com wrote:
What shall happen to davfs2.SlackBuild? It is still in the 12.2 and
12.1 repositories
What shall happen to davfs2.SlackBuild? It is still in the 12.2 and
12.1 repositories and it worked on my Slack64-13.
From the ChangeLog:
The following entries were not checked at all for 13.0, as we simply ran
out of time to do them. We know that some of these were likely mentioned
on the
Hi All,
Not being competent as Alien Bob or Heinz Wiesinger, I must say that I only
managed to install virtualbox-ose-x86_64-1_Sbo.tgz on Slack64 after a heavy
trial and error session. For those who are planning to make such an
installation the following notes might help. If anyone can explain or
Hi,
I noticed some errors in my vlock/README submission. A new improved version
is attached. Kindly replace it.
Cheers
Chris
vlock.tar.gz
Description: GNU Zip compressed data
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
Hi All,
1. The gc.SlackBuild puts the man file in /usr/man/man1/
mkdir -p $PKG/usr/man/man1
mv $PKG/usr/share/gc/gc.man $PKG/usr/man/man1/gc.1
gzip -9 $PKG/usr/man/man1/gc.1
While the first line in the man file suggests that this is the correct
place, I suspect that gc is a C library
Further to a discussion that ensued on a linuxquestions.org thread:
http://www.linuxquestions.org/questions/slackware-14/virtualbox-2.1.2-slackb
uild-699309/
I noted that the permissions on rc-scripts installed by Slackbuild packages
are not consistent. Moreover the default permissions are not
99 matches
Mail list logo