Re: [Slackbuilds-users] Questions about SlackBuild licenses

[JK Wood]

On Thu, Jul 29, 2021, 20:38 Dave Woodfall  wrote:

> On 30/07/21 02:43,
> Edward Ender  put forth the proposition:
> >I know that each SlackBuild must include a license block, but what
> about these off-brand licenses like WTFPL, etc?
> >Are these legit or should they be changed to the MIT-style block?
> >Is there a list of "accepted" licenses? Or should they just follow
> the OSI standards?
> >Thanks,
> >Ed
>
> Ben / Urchlay uses WTFPL so I assume any off-brand is OK.  We don't
> have a list of accepted licenses that I know about.
>
> --
> Dave
> ___
> 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/


My understanding is that the licenses have to ensure the rights of the end
user to modify them. Public domain does not exist in all jurisdictions, so
the license has to specifically give rights to the end user to ensure that
it's useable everywhere by everyone. See any of my SlackBuilds for pretty
much the minimal acceptable license.

--JK

>
>
___
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] Converting other packages to .tgz

[JK Wood]

On Mon, Jun 1, 2020, 12:42 Klaatu  wrote:

> On Monday, June 01, 2020 08:11:43 AM Rich Shepard wrote:
> > I'm curious because core slackware provides a great utility, rpm2tgz, but
> > not one for .deb packages. Yet, a number of SBo packages download a .deb
> and
> > convert it to .tgz for installation. Why the difference(s)?
> >
> > Regards,
> >
> > Rich
> > ___
> > 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/
>
> When I use a .deb file as source, it's usually because the latest RPM is
> Fedora
> and requires a very recent libc or libc++ (or similar) that my Slackware
> box
> doesn't have by default. The .deb packages I find seem to be more
> conservative,
> whether for Debian or Ubuntu LTS.
>
> My first response to that is to look for an RPM from CentOS or RHEL, which
> also
> tend to be conservative, but their repos just aren't as well stocked as
> Debian's, so .deb is often the best and easiest solution.
>
> -klaatu___
> 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/


If you look at the Google Chrome SlackBuild on /extra it shows how to deal
with .deb packages. There's really no need for a dedicated tool there.

Thanks,
JK

>
>
___
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] liblxi and lxi-tools up for adoption

[JK Wood]

Hi,

I can take these over. It may be next week before I can get an update
together - DnD tonight, oncall all weekend.

--JK

On Fri, Feb 21, 2020, 15:15 Nate Bargmann  wrote:

> Hi All.
>
> I still have the lxi-tools and liblxi package scripts available for
> adoption.  These two packages are for network access and control of
> electronic test equipment such as oscilloscopes, volt-ohmmeters, signal
> generators, some power supplies, and the like.
>
> They can be useful programs for electronics hobbyists.
>
> - Nate
>
> --
>
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
>
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
> ___
> 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] Giving up my packages to another maintainer

[JK Wood]

On Thu, Jan 9, 2020, 18:46 Nate Bargmann  wrote:

> First off, I want to say thanks to everyone who keeps SBo going.  It is
> such a fantastic resource for those running Slackware.  Over a year ago
> I moved back to Debian and have been maintaining nine package scripts
> simply to maintain a connection to the distribution that I started with
> back in '96.  Oh, what a resource this site would have been back then!
>
> Anyway, some changes in my personal life are going to be occupying more
> of my free time in the months and maybe years ahead.  I think it is
> better to offer these scripts now rather than fall behind and become a
> non-responsive maintainer.
>
> The packages are mostly ham radio related:
>
> development/astyle
> ham/hamlib  (I am currently the upstream for this)
> ham/qrq
> ham/tlf
> ham/wsjtx
> ham/xdx (I am currently the upstream for this)
> ham/xlog
> libraries/liblxi
> network/lxi-tools
>
>
> Thanks for letting me be a small part of this community for a while.
>
> - Nate
>
> --
>
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
>
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
> ___
> 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/


Hi Nate,

Thanks for the hard work! You've done a great job.

I'll be happy to take the ham packages. I'm using wsjtx as we speak - 6m is
open!

Thanks,
JK Wood, N0ES

>
>
___
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] Unmaintained builds - want any of these?

[JK Wood]

On Thu, Jan 2, 2020, 02:41 Robby Workman  wrote:

> Hello all,
>
> TL;DR version: if you would like to see any of the scripts on the
> following list stay around, please step up to maintain them.
>
> https://slackbuilds.org/DeadSBoBuilds
>
> Reply with which script you want, how you want to be listed in
> the .info file, and what email address you want listed there.
>
> Longer version: we're coming to terms with the fact that we
> simply don't have the personnel or the time to maintain all of
> the scripts here ourselves, so we (translation: B. Watson) ran
> through a got some lists of stuff that hasn't had any recent
> commits by their listed maintainers. The list posted above is
> NOT all of them - it's only the first batch (we're trying to keep
> this in bite-sized chunks). We don't have a specific timeline
> in mind at this point, but I'm thinking that any of these not
> claimed within a month or so will be removed from the repo.
>
> As always, thanks to our community for your support over the
> years!
>
> -RW
> ___
> 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/



I'll take these:

ham/7plus
ham/cwstation

Same maintainer info as ham/xpsk31 (sorry, on my phone.)


Thanks,

JK
___
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] jdk wrong checksum.

[JK Wood]

That's not entirely accurate. They can no longer be downloaded by sbopkg,
but they will build fine if you download the files manually and place them
in /var/cache/sbopkg (I believe, not at my computer to verify.

--JK

On Thu, Apr 11, 2019, 16:15 Dave Woodfall  wrote:

> On Thursday 11 April 2019 15:08,
> Fernando Lopez  put forth the proposition:
> > slackbuilds   org/repository/14.2/development/jdk/
> >
> > Processing jdk
> >
> > jdk:
> > Found jdk-8u202-linux-x64.tar.gz in /var/cache/sbopkg.
> > Checking MD5SUM:
> >   MD5SUM check for jdk-8u202-linux-x64.tar.gz ... FAILED!
> > Expected: 0029351f7a946f6c05b582100c7d45b7
> > Found:81ee08846975d4b8d46acf3b6eddf103
> >
> > Do you want to use the downloaded jdk source:
> > jdk-8u202-linux-x64.tar.gz in /var/cache/sbopkg?
> >
> > You can choose among the following options:
> >  - (Y)es, keep the source and continue the build process;
> >  - (N)o, delete the source and abort the build process;
> >  - (R)etry download and continue the build process; or
> >  - (A)ttempt to download from third party source repository.
> > (Y)es, (N)o, (R)etry, (A)lternative ?:
>
> Unfortunately, jdk or jre can no longer be built with sbopkg because
> the source has to be downloaded manually after agreeing to the
> license.
>
> The only solution is to grab the files and build it manually, or
> perhaps use openjdk or one of alienBOB's packages.
>
> --
>
> "Eat, drink, and be merry, for tomorrow you may work."
> ___
> 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] Compatibility of build scripts for Slackware64 + multilib at SBo

[JK Wood]

On Wed, Jan 23, 2019, 12:54 Fellype  Hi all,
>
> I have a question:
> If I write a Slackbuild script on a machine that has installed
> Slackware64 (stable, of course) + multilib, will the script be compatible
> with SBo?
>
> I'm asking this because I'm the maintainer of some build scripts and I'm
> considering to move all the machines I've Slackware installed to
> Slackware64 + multilib. So I'll not have a pure 32/64 bits machine to make
> tests and I don't want to provide/submit scripts that works only for me.
> I tried to find the answer for this question in the SBo's FAQ and mail
> list archives, but it was not much clear for me...
>
> Thanks in advance and best regards.
>
> Fellype
>
> ___
> 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/


I use two virtual machines for testing my builds that are otherwise clean,
and reset the images after testing. There are a lot of advantages to doing
it this way.

Thanks,
JK
___
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] driftnet slackbuild

[JK Wood]

On May 2, 2017 13:27, "Brenton Earl"  wrote:

Hello,

The driftnet SlackBuild has significant new development.  The new
release can be found here:

https://github.com/deiv/driftnet

It appears that you have been inactive for quite some time.  I can take
over maintenance if you are no longer interested in maintaining
driftnet.

Thanks,
Brenton



Hi Brenton,

You're welcome to take over driftnet. I had some build problems the last
time I took a look at it, but hopefully that's been resolved.

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

Re: [Slackbuilds-users] Submission rejected.

[JK Wood]

On Nov 15, 2016 12:45, "Didier Spaier"  wrote:
>
> Le 15/11/2016 à 19:10, Didier Spaier a écrit :
> > Got this as upload result:
> > ...
>
> PS: in case someone wonder: of course no "~" in the submission form.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

The email is used to send you a link that will allow you to withdraw the
upload in case you need to modify it for some reason. That's all they use
the address for - it doesn't go into a public list and they won't use it to
contact you.

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

Re: [Slackbuilds-users] Problem building qt5 on 14.2

[JK Wood]

On Aug 29, 2016 14:38, "fl...@mclink.it"  wrote:
>
> Il 29/08/2016 13:27, Willy Sudiarto Raharjo ha scritto:
>>>
>>> I think it is clearly RAM related. Either RAM is too low (I was using 8
GB) or bad.
>>
>>  I don't think it's low RAM issue as i use 2 GB of RAM for my VM and it
still built fine
>>
>>
>>
>> ___ SlackBuilds-users
mailing list SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives -
https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
https://slackbuilds.org/faq/
>
> I tried various RAM configurations (8 GB, 16 GB) and swapped RAM modules
and still got the error.
>
> I tested all the RAM with memtest. Maybe in a VM the conditions are
different and the problem does not appear.
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

Have you checked the size of /tmp? You would think that it would give you a
space error, but I've seen a full /tmp give strange compile warnings before.

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

Re: [Slackbuilds-users] Optional dependencies in info file

[JK Wood]

On Nov 30, 2015 4:44 AM, "Andrzej Telszewski"  wrote:
>
> On 30/11/15 11:13, Didier Spaier wrote:
>>
>> On 30/11/2015 10:13, Andrzej Telszewski wrote:
>>>
>>> On 30/11/15 00:31, Christoph Willing wrote:

 On 11/30/2015 09:11 AM, Andrzej Telszewski wrote:
>
> On 29/11/15 23:56, Christoph Willing wrote:
>>
>> The only work is adding the options you want but that is also the
>> advantage - you have the options _you_ want rather some some
arbitrary
>> set of options the maintainer wants or believes end users will want.
>
>
> Actually, it's like that at the moment and it always will be like
that.
> I mean you will always have some choices that you can or not adjust to
> your needs.
>
> The difference is that "optional options" are mentioned in README,
> whereas "required options" are placed in info - you put the optional
> deps in *.info, which gives the whole thing better structure.
>
> But it is always *YOU* who has to make the choice, the difference is
how
> the information about possible dependencies is given to you.


 We need to bear in mind the difference between options and
dependencies.
 An added option may, or may not, entail an added build dependency i.e.
 any added ENVOPTS (or whatever) field _may_ need adjustment to the
 REQUIRED field too. In order to keep existing .info fields pristine, I
 use an additional PREREQS field to keep track of additional
 dependencies, leaving the REQUIRED field intact.
>>>
>>>
>>> I think we understand each other, it's just wording that's awkward.
>>>
>>> I would see it more less (without longer thinking) like that:
>>> - additional file for optional dependencies, together with the
>>> environment variable (if applicable),
>>> - additional file for environment variables that do not require software
>>> dependency.
>>>
>>> That would require at least 2 things:
>>> - forcing SlackBuild-s creators to use the particular structure - that's
>>> not a problem, because SBo already has some requirements,
>>
>> Good luck to get that done, but do not hold your breath.
>>
>>> - making the website processing additional information to display it to
>>> the user; it's important, because it would be error prone to expect the
>>> SlackBuild creator to maintain README and additional meta-data files in
>>> sync.
>>
>> I will let the website maintainers and admins answer that.
>>
>> I am reluctant.
>> _ If a dependency is optional it's up to a human being to take or refuse
it.
>> _ We have already a lot of (I almost wrote "too many") package managers,
as
>>listed by David (thanks again for the list):
>>  http://idlemoor.github.io/slackrepo/links.html
>>It would take a lot of time to modify all of them accordingly.
>> _ Along the time package managers naturally tend to provide more and more
>>features less and less useful, that just complicate their usage and
>>sometimes introduce bugs.
>> _ Some features, although they be useful, exist since a long time and
come
>>handy, are probably not used by many folks, like editing a SlackBuild
or
>>a .info from sbopkg. The more features, the more time needed by end
users
>>to use them.
>> _ It is not that difficult to list optional dependencies in a SlackBuild
>>if the target audience is human beings, not computer propgrams.
>>This is just an example:
>>  http://slackbuilds.org/repository/14.1/misc/po4a/
>>
>>> Still, is it worth?
>>
>> No, IMHO.
>
>
> Well, I too think that it would be much work, it's probably not worth it.
>
> What is your opinion on the READMEs? For me it was the culprit, that made
me propose what I've proposed. It's my personal opinion, but the READMEs
are not well readable;)
>
> I would propose to allow markdown in READMEs, but still, the maintainers
would have to use it in consistent way.
>
> I know one should read the READMEs thoroughly, but it's much easier to
spot what's important, if it's *for example in bold*.
>
> Like any other well written software, SBo deserves good documentation:)
>
> I don't think we'll go much further with that for a moment;)
>
>
>>
>> I hope that this negative answer will not discourage you. We do need
folks
>> to make proposals, be they accepted or not, so thanks for this one
Andrzej.
>
>
> No worries:)
>
>
>>
>> Bien cordialement.
>> Best regards,
>> Pozdrawiam.
>
>
> Saludos cordiales:)
>
>
>>
>> Didier
>> ___
>> 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/
>>
>>
>
>
> --
> Pozdrawiam,
> Best regards,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> 

Re: [Slackbuilds-users] Scripts Available for Maintainers

[JK Wood]

> ham/xlog
> ham/hamlib
> ham/qrq

I can take these.

--JK
___
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] Keywords in info file

[JK Wood]

The other thing to keep in mind is this: the database keeps track of the
keywords that have already been associated with the SlackBuild. The only
reason you would need to worry about that after the original submission is
if you come up with additional keywords, which shouldn't happen often
unless you're dealing with systemd-level feature creep.

--JK

On Mon, Sep 7, 2015 at 5:34 PM, David Spencer <
baildon.resea...@googlemail.com> wrote:

> > I will keep the keywords in a separate file and just won't include it in
> the
> > upload.
>
> How about using dokuwiki? It's how I keep all my maintaining info,
> including version numbers, upstream URLs to check for new versions,
> mailing list and bugtracker URLs, other distro's packaging repos for
> stealing patches ;-) lists of packages that depend on my packages ...
> and keywords.
>
> There's an SBo package for dokuwiki, and Giorgio the maintainer
> updated it just a couple of days ago :-)
>
> -D.
> ___
> 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 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] smpeg compile weirdness?

[JK Wood]

On Jun 17, 2015 6:29 AM, Klaatu kla...@straightedgelinux.com wrote:

 OK, thanks. Must be something in my current env, or just something I'm
 doing weird. Thanks for the sanity check.

 -klaatu


 On 06/17/2015 10:49 PM, Matteo Bernardini wrote:
  2015-06-17 11:07 GMT+02:00 Klaatu kla...@straightedgelinux.com:
  Anybody else have a problem with building smpeg?
 
  I got it going, but I specifically had to configure with this:
 
  ./configure --libdir=/usr/lib64 --x-libraries=/usr/lib64
 
  as a straight configure kept attempting to default to /usr/lib/
 
  Could just be me; this was done on my multi-lib system, so quite
  possibly this is not seen on properly configured systems :-)
 
  dunno why but, FYI, here seems to use /usr/lib64: I tried on
  slackware64-14.1, slackware64-current and slackware64-current with
  multilib.
 
  Matteo
  ___
  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 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/


I've noticed on my multi-lib system that packages are inconsistent as to
which set of libraries they attempt to use. Haven't isolated why, though.

--JK
___
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] jack-audio-connection-kit vs jack2

[JK Wood]

On May 28, 2015 9:03 AM, Klaatu kla...@straightedgelinux.com wrote:

 On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
  I think in the future, I'll use %README% in REQUIRES to alert the user
  that the version of JACK is optional.
 
  %README% is used to tell users that a package is conflicting/replacing
  Slackware packages. Other than that, users are always assumed to read
  README.
 

 Willy,

 Is there currently a way to indicate that two packages are able to
 satisfy one dependency?

 I can't even think of an SBo precedence to base a resolution upon.

 -klaatu


Sure, there's the wxPython/wxGTK/wxWhateverTheOtherOneWas.

--JK ___
 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 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] Fwd: transmission make failure

[JK Wood]

On Sep 2, 2014 2:33 PM, Mats Bertil Tegner mats.bertil.teg...@gmail.com
wrote:

 On 2014-09-02 20:59, Yavor Atanasov wrote:


 Hello,
 Just try to upgrade my transmission package with sboupgrade and
 everything go fine until start compiling - then i get and error for
 missing aclocal and make error 127... Using Slackware 14.1. I
 posting here the error...

---
 configure: creating ./config.status
 config.status: creating Makefile
 config.status: creating transmission-gtk.spec
 config.status: creating cli/Makefile
 config.status: creating daemon/Makefile
 config.status: creating extras/Makefile
 config.status: creating libtransmission/Makefile
 config.status: creating utils/Makefile
 config.status: creating third-party/Makefile
 config.status: creating third-party/dht/Makefile
 config.status: creating third-party/libutp/Makefile
 config.status: creating third-party/libnatpmp/Makefile
 config.status: creating third-party/miniupnp/Makefile
 config.status: creating macosx/Makefile
 config.status: creating gtk/Makefile
 config.status: creating gtk/icons/Makefile
 config.status: creating qt/config.pri
 config.status: creating web/Makefile
 config.status: creating web/images/Makefile
 config.status: creating web/style/Makefile
 config.status: creating web/style/jqueryui/Makefile
 config.status: creating web/style/jqueryui/images/Makefile
 config.status: creating web/style/transmission/Makefile
 config.status: creating web/style/transmission/images/Makefile
 config.status: creating
web/style/transmission/images/buttons/Makefile
 config.status: creating web/javascript/Makefile
 config.status: creating web/javascript/jquery/Makefile
 config.status: creating po/Makefile.in
 config.status: executing depfiles commands
 config.status: executing libtool commands
 config.status: executing default-1 commands
 config.status: executing po/stamp-it commands

 Configuration:

 Source code location:  .
 Compiler:
 i486-slackware-linux-g++

 Build libtransmission: yes
* optimized for low-resource systems:   no
* µTP enabled:  yes

 Build Command-Line client: yes

 Build GTK+ client: yes
* libappindicator for an Ubuntu-style tray: no

 Build Daemon:  yes

 Build Mac client:  no


 CDPATH=${ZSH_VERSION+.}:  cd .  /bin/sh
 /tmp/SBo/transmission-2.84/missing aclocal-1.14 -I m4
 /tmp/SBo/transmission-2.84/missing: line 81: aclocal-1.14: command
 not found
 WARNING: 'aclocal-1.14' is missing on your system.
   You should only need it if you modified 'acinclude.m4' or
   'configure.ac' or m4 files included by 'configure.ac'.
   The 'aclocal' program is part of the GNU Automake package:
   http://www.gnu.org/software/automake
   It also requires GNU Autoconf, GNU m4 and Perl in order to
 run:
   http://www.gnu.org/software/autoconf
   http://www.gnu.org/software/m4/
   http://www.perl.org/
 make: *** [aclocal.m4] Error 127
 Failures:
transmission: transmission.SlackBuild return non-zero

--
 Any help will be appreciated guys... :-)


 Hello,
 You'll need to upgrade to automake 1.14.1 in order to build transmission
2.84. The following line also needs to be added to the SlackBuild otherwise
building the Qt-client will fail with Qt4:

 sed -i '/^CONFIG/aQMAKE_CXXFLAGS += -std=c++11' qt/qtr.pro

 Mats



If it doesn't build on a stock 14.1 Slackware, why is it on SBo?

--JK
___
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] Panagiotis, please add me to your LinkedIn network

[JK Wood]

Can we not spam the whole list when setting up LinkedIn?

/me wanders off grumbling about social media email harvesting scams

--JK
___
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] SlackBuilds TQSL

[JK Wood]

On Jul 17, 2014 9:26 AM, Richard Morton rmfla1...@gmail.com wrote:

 Hello


 For your TQSL SlackBuild the tqsl.SlackBuild script should be version
2.0.1 not 2.0.2
 After starting TQSL there is pop-up to a URL to the new version 2.0.2
 So you would have to rebuild it again and update.


 Thank you
 Richard Morton

Whoops! I fixed it in the SlackBuild and in the VERSION, but not the
DOWNLOAD (or the MD5SUM, I assume.)

Incrementing the version in the .info file (and fixing the md5 if needed)
will fix this. I can submit an update in about 5 hours to fix the problem.

Thanks for the report!

Thanks,
JK
___
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] SlackBuilds TQSL

[JK Wood]

On Jul 17, 2014 1:00 PM, Willy Sudiarto Raharjo will...@slackbuilds.org
wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

  Incrementing the version in the .info file (and fixing the md5 if
needed)
  will fix this. I can submit an update in about 5 hours to fix the
problem.

 I have fixed this on my branch
 no need to submit an update

 - --
 Willy Sudiarto Raharjo
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iEYEARECAAYFAlPIDysACgkQiHuDdNczM4HsMACfUUV+9J4SnIkYYExJ6THhzvsX
 BLwAoIf85VGs2/VpIug49qellay6RVGH
 =Rtix
 -END PGP SIGNATURE-


Thanks Willy!

Thanks,
JK
___
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] commercial software buildscripts

[JK Wood]

On Apr 16, 2014 4:26 PM, Miguel De Anda mig...@thedeanda.com wrote:

 what's the sbo/slackware policy on commercial software?

 i've created a slackbuild for smartsvn (and i'll port it over for their
git solution as well) but i'm hesitant to upload it. the script doesn't
include any commercial or non-open source bits but the .info file would
link directly to their binary. upon first launch it typically asks you to
accept their agreement and choose from a feature-limited free (as in beer)
version or to upload the license file.

 i create the build script simply because i wanted a launcher.

 regards,
 miguel de anda

 ___
 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/



Should be fine. There are plenty of closed source and pay-for software
packaging scripts in the SBo repository, and then there are pieces like the
JDK where you have to accept a license agreement before downloading.

Just don't distribute the software yourself - point to the original source
and you'll be fine.

--JK
___
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] libs in /usr/local/lib

[JK Wood]

On Mar 9, 2014 8:52 AM, Nick Warne n...@linicks.net wrote:

 On 09/03/14 13:39, Nick Warne wrote:

 On 09/03/14 13:35, Didier Spaier wrote:

 On 09/03/2014 14:30, Nick Warne wrote:



 On 09/03/14 13:19, Didier Spaier wrote:

 On 09/03/2014 13:36, Nick Warne wrote:

 Using slackbuild dsniff (as an example), I find that slackbuild
fails on ./configure as it thinks libnet is not installed.

 Now, not to confuse things, this is on my AMD64 running Slack 12.1
(no multilib) and I often build/install 'lesser used libs' into
/usr/local/lib and run/update ldconfig on installation.

 I can configure dsniff by hand fine, all libs are found - but using
the slack script, it doesn't find them...


 Alla SlackBuilds for libnet (there is none fo Salcakre 12.1) include
this:

 elif [ $ARCH = x86_64 ]; then
 SLKCFLAGS=-O2 -fPIC
 LIBDIRSUFFIX=64

 So this configure option:
 --libdir=/usr/lib${LIBDIRSUFFIX} \
 expands to:
 --libdir=/usr/lib64

 But there is no /usr/lib64 directory in Slackware 12.1.

 Could that be the issue?


 I looked at that - forgot to say too that this was a Slamd64 distro
before Pat made the official 64bit build, so I do have a /usr/lib64 (for
years).

 All those $VARS do in the build is where to install the package libs
(if you use it).

 And it doesn't matter where the libs are installed to - the 'system'
knows they are there ref. ldconfig and a manual ./configure works...


 Then, would you mind posting your full (with all options) manual
configure command that works?


 Yes, sure:

 ./configure

 :)

 This is nothing to do with the slackbuild of dsniff!  I just used that
 as an example (as this is when I found this issue).

 I just do not know why the slackbuild ./configure doesn't see libnet
 libs in /usr/local/lib yet the system does!

 Nick


 OK, I was thinking, I use 'sudo' and wondered if it was an ENV thing
going on:

 sudo ./dsniff.Slackbuild
 ...
 checking for Berkeley DB with 1.85 compatibility... yes
 checking for libpcap... yes
 checking for libnet... no
 configure: error: libnet not found

 Now log in as 'real' root:

 ./dsniff.Slackbuild
 ...
 checking for Berkeley DB with 1.85 compatibility... yes
 checking for libpcap... yes
 checking for libnet... no
 configure: error: libnet not found

 Now as normal user (me) in dsniff directory:

 ./configure
 ...
 checking for Berkeley DB with 1.85 compatibility... yes
 checking for libpcap... yes
 checking for libnet... yes
 checking for libnids... yes
 checking whether libnids version is good... yes
 checking for OpenSSL... yes
 creating ./config.status
 creating Makefile
 creating config.h
 config.h is unchanged

 Huh!  See what I mean?


 Nick
 --
 A bug in the code is worth two in the documentation.
 FSF Associate Member 5508
 http://linicks.net/
 http://pi.linicks.net/
 ___
 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/


There's your issue (most likely). SlackBuilds from SBo are meant to be run
as root. If you must use sudo, use sudo su - and run from there.

-JK
___
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] google chrome

[JK Wood]

It was removed (I believe) because there's a build script for google-chrome
in /extra:

http://taper.alienbase.nl/mirrors/slackware/slackware-14.1/extra/google-chrome/

-- JK


On Mon, Feb 17, 2014 at 3:50 PM, Miguel De Anda mig...@thedeanda.comwrote:

 is google chrome no longer supported? i was able to build it with only
 minor changes to the 13.1 script on the site (they moved the .desktop file
 so the 'ln -s' line is no longer needed and the path to the .desktop file
 modified by sed needs to change.

 i use chromium but there are sometimes minor differences ( html5test.comshows 
 different scores) so i'm trying to use both browsers even though i
 mostly use chromium.

 -m

 ___
 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 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] Updates - 20131217.1

[JK Wood]

On Dec 17, 2013 11:15 AM, Erik Hanson e...@slackbuilds.org wrote:

 Tue Dec 17 17:03:59 UTC 2013
 academic/gwyddion: Updated for version 2.34.
 academic/horao: Added (visualisation tool for 3D GIS data).
 audio/mp3splt-gtk: New Maintainer.
 audio/mp3splt: New Maintainer.
 audio/soundkonverter: New Maintainer.
 desktop/bspwm: Added (Binary space partitioning window manager).
 desktop/lxmed: Changed maintainer.
 desktop/menulibre: New Maintainer.
 desktop/sxhkd: Added (Simple X hotkey daemon).
 development/amaya: Removed (not compatible with gcc-4.8.x).
 development/squirrel-sql: Updated for version 3.5.0.
 libraries/libmp3splt: New Maintainer.
 libraries/libpst: New Maintainer.
 libraries/qt5: Added (multi-platform C++ GUI toolkit).
 libraries/zend-opcache: Updated for version 7.0.2.
 multimedia/w_scan: New Maintainer.
 network/hydra: Updated for version 7.5.
 network/icecat: Updated for version 24.0.
 network/midori: Updated for version 0.5.6.
 network/smcroute: Added (Static Multicast Routing Daemon).
 network/sstp-client: Added (SSTP client for Linux).
 office/calibre: Updated for version 1.15.0.
 office/hevea: Updated for version 2.09.
 perl/perl-Class-Method-Modifiers: Updated for version 2.09.
 perl/perl-Date-Manip: Fix download link.
 perl/perl-strictures: Updated for version 1.005002.
 python/python-ldap: Added (Python modules for LDAP clients).
 python/vatnumber: Added (Python module to validate VAT numbers).
 system/linuxconsoletools: New Maintainer.
 system/nvidia-driver: Updated for version 331.20.
 system/nvidia-kernel: Updated for version 331.20, cleanups.
 system/sdl-jstest: New Maintainer.
 system/udevil: Updated for version 0.4.3.
 system/xboxdrv-linux: New maintainer.
 system/zerofree: New Maintainer.

 ___
 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/



Just wanted to point out that Nvidia 331.20 breaks several Steam games for
me in Wine (the primary one for me being Terraria.) I've seen evidence from
others that it breaks lots of Mono-related things.

Thanks,
JK
___
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] Package for TLP

[JK Wood]

On Nov 19, 2013 11:15 AM, Aaditya Bagga abchk1...@gmail.com wrote:

 Aaditya Bagga wrote:

 Aaditya Bagga wrote:

 Hey folks!

 I have built a package for TLP.

 http://linrunner.de/en/tlp/tlp.html
 http://linrunner.de/en/tlp/docs/tlp-developer-documentation.html
 https://github.com/linrunner/TLP

 The SlackBuild
 http://sourceforge.net/projects/mefiles/files/TLP.tar.gz

 The Source
 https://github.com/linrunner/TLP/archive/0.4.tar.gz

 Its my first SlackBuild so..
 I built it and installed it my side.

 Note-
 See the develepor-documentation linked above.
 They have some post install tasks, which I have included in doinst.sh,
but there are also some post-remove tasks, which I dont how to incorporate.

 Ok, I tried to improve upon the build script by modifying the
configuration files that were being placed in /etc/init.d are now placed as
/etc/rc.d/rc.tlp
 (The same SlackBuild linked above has been updated)

 But I still need to figure out how to add the tlp service to startup..

 Ok, I think I figured out how to add it to startup..add it to
/etc/rc.d/rc.local, set in doinst.sh
 so thats done.

 But still dont know how to perform post-removal tasks like removal of
this line from rc.local or the other settings done in doinst.sh..

 ___
 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/


Generally, you want to avoid messing with the user's rc.local. I'd include
information on how to add it to rc.local to the README and let them deal
with it. You could wrap it in a check for rc.tdp existing so that there's
no problem after uninstall, I suppose.

Thanks,
JK
___
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] PostgreSQL - multiple installed versions

[JK Wood]

On Sep 3, 2013 10:03 PM, Benjamin Trigona-Harany bo...@alumni.sfu.ca
wrote:

 On September 3, 2013 17:04:15 Adis Nezirovic wrote:
  Guys, I have a question for all PostgreSQL users and SBo admins.
 
  Would it be OK for the next PostgreSQL package (upcoming 9.3) to be
version
  specific and parallel-installable with  old PostgreSQL versions.
  (of course, we would continue that practice in the future).
 
  Since PostgreSQL installations are not upgradeable in place, one needs
to
  do export/import data cycle or use pg_upgrade utility, and having old
and
  new database instance would be very handy for that.
 
  The packages would be named postgresql93 (v9.3.x), postgresql94 (v9.4.x)
  (the current postgresql can be treated as postgresql92), and would use
  version specific data directories.

 This is timely because a similar issue just came up with the 2.2 release
of
 PostGIS, which also expects both the current 2.2 and the previous 2.1
versions
 installed to do an in-place upgrade of existing databases.

 However, providing both postgis21 and postgis22 SlackBuilds would mean
some
 headaches for packages depending on PostGIS since it wouldn't be evident
which
 version of PostGIS it was built against without also versioning that build
 script.

 Likewise, splitting PostgreSQL into version-dependent scripts is going to
 affect dependencies. Other distros have ended up with packages such as
 postgres91-postgis21-2.1.0, but I don't see that being maintainable,
 especially when we consider the further SlackBuilds that will depend on
that
 package.

 Ben
 ___
 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/



Speaking as someone who works with databases professionally, if you don't
have a way of maintaining an upgrade path you have bigger problems.

Speaking as someone who maintains a few packages, having two differing
packages won't solve the problem, which is overwriting the tools when you
install the new package.

It really sounds to me like an upgrade script which takes care of the
necessary steps for an upgrade would be infinitely preferable, and should
be done in addition to the current SlackBuild.

--JK
___
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] Desmume on 64-bit - optimization flag

[JK Wood]

On Jan 23, 2013 7:47 PM, xgiz...@slackbuilds.org wrote:

 On Wednesday 23 January 2013 10:01:12 Matteo Bernardini wrote:
  Hi J,
 
  I tried to adapt the line to take in account Eric's advices
 
  SLKCFLAGS=${SLKCFLAGS:--O2}
  LIBDIRSUFFIX=
  [ $(uname -m) = x86_64 ]  [ ! $(echo $PATH | grep
^\/usr\/bin\/32)
  ]  SLKCFLAGS=$SLKCFLAGS -fPIC LIBDIRSUFFIX=64
  [ $ARCH = i486 ] || [ $ARCH = native ]  SLKCFLAGS=$SLKCFLAGS
  -march=$ARCH
  [ $ARCH = i486 ] || [ $ARCH = i686 ]  SLKCFLAGS=$SLKCFLAGS
  -mtune=i686
 
  Matteo
 
  P.S. just to be clear, this is for fun only: ATM there's no plans to
change
  anything regarding custom CFLAGS/ARCH detection.
 

 I think all that would be needed is to add a line after the $SLKCFLAGS
block.

 if [ -n $RICER_FLAGS ]; t--hen SLKCFLAGS=$RICER_FLAGS; fi

 Then run your build  RICER_FLAGS=-enable-more-fruitloops
./some.SlackBuild

 --dsomero :)


Just remember, using a red R in Slackware gives you better acceleration,
but using a yellow R increases your top speed.

-JK ___
 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 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] sbopkg and the README/.info files (REQUIRES line)

[JK Wood]

On Mon, Oct 8, 2012 at 5:03 PM, slakmagik slakma...@gmail.com wrote:

 Hi. :)

 For a similar case, I just removed a defunct repo file and we probably
 should never have included any non-SBo repo. It's easy for the user to
 integrate their own unofficial repo files in the repos directory.
 Similarly, while Mauro's helped develop sbopkg, it and the queuefile
 projects are separate things and, if he stopped maintaining the
 queuefiles, I'd have to take out what I'd just put in. It's easy for the
 user to put the files into the queuedir if they want. Also, anyone can
 have a queufile project. If anyone's project was to be privileged, it'd
 be his, but I'd rather no single queuefile project was privileged and I
 don't want to try to deal with an indefinite number of them.
 ___
 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/


For the record, if I had realized that the Slamd64Builds repo was in
sbopkg, I would have had you disable it long ago.  It was a valiant effort,
but we were blindsided by the release of Slackware 64.

--JK
___
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] My SlackBuilds for 14.0

[JK Wood]

Hi all,

Here's the status of the SlackBuilds I maintain:

Working:
ham/fldigi: Already ready already, thanks to rworkman
development/cvsps: Builds fine here.

Patches attached:
libraries/libticables2: New package, necessary to build libticalcs2, tilem2
libraries/libticonv: New package, necessary to build libtifiles2,
libticalcs2, tilem2.
libraries/libtifiles2: New package, necessary to build libticalcs2, tilem2
libraries/libticalcs2: New package, necessary to build tilem2.
academic/tilem2: New package.
academic/tilem: Bumped build number, and noted in README that it will live
alongside TiLem2, but cannot be built while libticables2 is on the system.
games/freedroidrpg: Updated to 0.15.1.

Patches underway:
network/driftnet: Fails to build against libpng 1.4. Even though I
'patched' it to do so. I'll keep working at it.

Planned for the future: academic/tilp: New package, lets you dump roms for
use with tilem. Have to go vote, so it can probably wait until submissions
are open again.

--JK


0001-Updated-freedroidrpg-to-0.15.1.patch
Description: Binary data


0001-libraries-libticables2-Added-TI-Cables-Library-for-L.patch
Description: Binary data


0001-libraries-libticonv-Added-TI-Conversion-Library-for-.patch
Description: Binary data


0001-libraries-libtifiles2-Added-TI-File-Format-Library-f.patch
Description: Binary data


0001-libraries-libticalcs2-Added-TI-Calculator-Communicat.patch
Description: Binary data


0001-academic-tilem2-Added-TI-Calculator-Emulator-for-Lin.patch
Description: Binary data


0001-academic-tilem-Bumped-build-number-TI-Calculator-Emu.patch
Description: Binary data
___
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 'faenza-xfce'

[JK Wood]

On Tue, Aug 7, 2012 at 1:30 PM, Fridrich von Stauffenberg 
cancell...@gmail.com wrote:

 That's weird. Checked the link with wget and firefox, and it worked in
 both cases. Anyway, here's the mirror:


 http://dl.dropbox.com/u/11914640/shimmerproject-Faenza-Xfce-v.0.2.1-0-gd3e85cf.tar.gz

 07.08.2012 21:15, Nicolas Kovacs пишет:
  Le 05/08/2012 19:59, Fridrich von Stauffenberg a écrit :
  Yes, faenza-xfce is an add-on for the main faenza, which doesn't
  include some xfce-specific icons. Tried to rebuild it few minutes
  ago, and haven't got any errors (there's just nothing to break, as
  far as I can see). What exactly goes wrong?
 
  I checked again, with sbopkg as well as manually.
 
  Seems like the URL isn't valid anymore. No way to find the tarball
  the .info file is referring to.
 
  Niki
 
 ___
 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/


Works for me too. Can you get to github.com? Sounds like something's wonky
with your dns.

--JK
___
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] Slackware 14

[JK Wood]

On Aug 1, 2012 3:51 AM, Petar Petrov ppet...@mail.student.oulu.fi wrote:

 Quoting Eric Hameleers al...@slackbuilds.org:

 On 07/31/2012 08:37 PM, Petar Petrov wrote:

 Hi to all

 Since I joined SBo a year ago and have so far maintained scripts for
 only one Slackware release, I have the following question: What shall
 I do before the new Slackware release comes out? Am I supposed to
 start testing my slackbuilds when Slackware -current becomes RC1? Then
 if something needs patching, submit an update? The upload form is
 closed now, so what are you guys up to?

 Sorry if the questions sound silly, I read the mailing lists archives
 from a year ago when Slackware became 13.37, but did not find an answer.

 Regards,

 Petar

 Yes, that is the idea.
 If you test your SlackBuilds against Slackware 14 RC and report success
 (or send us updates) then that will help the admins immensely in getting
 a Slackware 14 repository live at the time of release.

 You will have noticed that with every new Slackware release, several
 SlackBuilds.org entries will disappear. The reason for this is that the
 maintainer has not reported whether his submission(s) work for the new
 release. The SlackBuild database is so big these days that the admins
 can no longer test all the scripts in the short time between closing the
 submissions form and the new Slackware release. We rely on the
 maintainers to tell us it's OK to copy scripts from one to the next
 database.

 Cheers, Eric
 ___
 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/


 Thanks for the clarification Eric!

 I don't want to sound like Are we there yet?, but are there any major
changes scheduled for Slackware14 yet to happen? Anything that I better
wait for, before I upgrade to -current and check how slackbuilds behave?

 Regards,

 Petar



 ___
 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/


If possible, you should have a dedicated development machine for testing
your SlackBuilds. You should preferably have a virtual machine that you can
reset to a clean install state between tests. And you should at least test
in a chroot.  Building on your desktop can be a valid test, but you really
need to know that what you maintain will build on a clean Slackware install
with only the noted dependencies installed.

You should preferably also test out the functions of the program just to
make sure you didn't miss any optional or runtime dependencies.

Remember, the more and higher quality testing you do, the less likely it is
that you have to scramble to fix foreseeable bugs.

--JK
___
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] Bad link for source on FLdigi

[JK Wood]

On Fri, Jul 27, 2012 at 2:38 PM, Robby Workman rwork...@slackbuilds.orgwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On Wed, 25 Jul 2012 10:52:03 -0400
 Ric Foust auto327...@hushmail.com wrote:

  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
Slackbuilds,
 
The source link for Fldigi no longer works. Also the latest
  Fldigi appears to be 3.21.49.


 CC'ing JK Wood on this...

 - -RW
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)

 iEYEARECAAYFAlAS7k4ACgkQvGy9tf6lsvu8SgCffWRhIPssweytiUZlEC93A9+n
 ehgAn0VdrasHWIrZMamPXP/ARgcqn/Q9
 =TpSe
 -END PGP SIGNATURE-


1) I love that signature, Ric.

2) Sorry about that. I've been a little lax on my SlackBuild updates lately
- I've moved three times in the past year, and have had some other life
events in between.  I'll try to get a new build submitted this evening, as
well as updating the rest of my SlackBuilds.
___
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] Bad link for source on FLdigi

[JK Wood]

On Fri, Jul 27, 2012 at 4:22 PM, JK Wood joshuakw...@gmail.com wrote:



 On Fri, Jul 27, 2012 at 2:38 PM, Robby Workman 
 rwork...@slackbuilds.orgwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On Wed, 25 Jul 2012 10:52:03 -0400
 Ric Foust auto327...@hushmail.com wrote:

  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
Slackbuilds,
 
The source link for Fldigi no longer works. Also the latest
  Fldigi appears to be 3.21.49.


 CC'ing JK Wood on this...

 - -RW
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)

 iEYEARECAAYFAlAS7k4ACgkQvGy9tf6lsvu8SgCffWRhIPssweytiUZlEC93A9+n
 ehgAn0VdrasHWIrZMamPXP/ARgcqn/Q9
 =TpSe
 -END PGP SIGNATURE-


 1) I love that signature, Ric.

 2) Sorry about that. I've been a little lax on my SlackBuild updates
 lately - I've moved three times in the past year, and have had some other
 life events in between.  I'll try to get a new build submitted this
 evening, as well as updating the rest of my SlackBuilds.



As anyone who has been paying any attention at all would know, I am unable
to submit a new script, since submissions are closed in anticipation of the
release of 14.0.

Anyone who wants an updated build script for fldigi can find it at my
Github repo (a fork of the official SlackBuilds.org repo) at
https://github.com/JKtheSlacker/slackbuilds. Do note that you'll want the
'jkwood' branch if you download through git. You'll still want that branch
if you just pull it from the website. I also moved it from the 'network'
category to the 'ham' category, as it more properly belongs there.
___
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] recode.SlackBuild

[JK Wood]

On Jul 11, 2012 1:11 PM, Chris Abela kristo...@gmail.com wrote:

 I was informed that the recode source link is dead. The source code is
however available from a git repositoryhttps://github.com/pinard/recode
 As I am not using recode anymore, I am offering the maintenance of the
SlackBuild to anyone willing to take up the job.

 Also, any offers to host the source code would be appreciated as I do not
own a server. For the time being the source code may be downloaded from my
dropbox account:
 https://dl.dropbox.com/u/49744080/recode-3.6.tar.gz

 Chris Abela



GitHub has a free download service for all projects. They really should be
using that.
___
 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 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] requirements in README files

[JK Wood]

On Jul 10, 2012 7:00 AM, David Spencer baildon.resea...@googlemail.com
wrote:

 For the record I'm personally not 100% hostile to the idea.  I could
 live with a formal mechanism for declaring mandatory direct
 dependencies, but I wouldn't stay up late myself to make it happen.
 If it ever did happen, I'd hope that both build-time and run-time
 dependencies should be included with no distinction.  The end users
 would be freaked out if packages failed to run despite meeting what
 they would see as formally documented deps.

 It's reassuring that nobody is advocating version dependency, you know
 the sort of thing: gnome-stuff = 2.34.56.  You're not all completely
 mad and I respect you for that :D

But, that's exactly the problem. Sometimes, there is a minimum necessary
version required to build a package. Other times, there is a maximum
required (I'm thinking of Python in particular, but I know there are other,
non-official packages that have had this problem.) In theory, the current
admin system in use at SBo should keep this from being a problem. In
practice, maybe not.

But then, we can't really just include version information, because that's
a whole nother ball of wax. What's newer, 1.54 or r1076?


  This requires zope.component and gaphas 

 Just imagine the chaos for automatic parsing if there was a package
 named 'and' :-)

 -D.

And what if more than one package fits the bill? The wxWidgets packages
come to mind. I believe at one point, there were three different packages,
any of which would satisfy that one dependency, and any of which required a
fairly large source download and a fairly lengthy compile. You definitely
didn't want to build all three!

 ___
 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 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] requirements in README files

[JK Wood]

On Jul 10, 2012 11:31 AM, J j...@dawnrazor.net wrote:


 Well, morning folks. why is it always morning when one works nightshift?
so not fair. anyway.

 so, first off, sbotools already exists and has some requirement-parsing,
it is how I deal with slackbuilds.org myself. and I continue to hack on the
parsing code to improve it for the gazillion corner-cases.

 so let's talk about some of the irrelevancies that keep cropping up for a
moment, so that we can hopefully stop talking about them, stop all this
bikeshedding, and focus on the subject at hand.

 1. portage - I don't think anyone here has any interest in duplicating
that mess. I certainly don't.
 2. the slackware way - if you feel that manually dealing with your  sbo
requirements keep you true and pure to the way - fine, so what, and who
cares? this has nothing to do with you, so please stop bikeshedding.

Maintainer of a number of scripts here. This has EVERYTHING to do with us.
You're asking me to take it upon myself to make a change that doesn't
benefit me, but benefits you? A change that allows you to go against the
philosophy that I subscribe to? Good luck, friend.

 3. Buildtime, optional, etc - I talked about this already. I am only
interested in consistency about how hard and fast requirements are
documented in README files, and that is *it*. I am not interested in
changing anything else, anywhere, including how optional dependencies are
or are not documented.
 4. sbopkg and queue files - that idea is cool, but as a solution to this
problem it represents not only a massive repeating of work, but also a
massive amount of extremely inelegant brute-forcing.

 I've seen a few times mention of adding this stuff to the SlackBuild, or
a separate file. As I mentioned, that would be ideal - it is by the far the
easiest solution to handle programatically. but it doesn't make sense here,
and I personally am not terribly interested in seeing this happen.
requirements *must* be listed in the README - so, since they're there
already, that will do, if we can get some consistency. With that, then in
the following case:


 Quoting Christoph Willing c.will...@uq.edu.au:

 specify the build depenednecies but over the last year or so I have been
modifying SBo scripts (when they already exist) to include a PREREQS= line
in the info file. If PREREQS were already included, I wouldn't have to
maintain my own versions of them. However the effort in doing so is worth
it, so I do.


 Christoph could easily write his own parser to deal with his use-case.

 anyway.


 Quoting TuxaneMedia j...@tuxane.com:

 The admins do alter README files and it looks like this is getting the
 way to go:

 This requires zope.component and gaphas 


 is this absolute fact? can we get some admins to chime in? if this is
fact, and all admins are doing it and following the same format, then this
means that for 14.0 we'll have consistency, and my work here is done.


 Quoting Chess Griffin ch...@chessgriffin.com:

 Finally, and here is where I put on my former SBo admin hat on, if the
 SBo project were to change things and start requiring that build-time
 dependencies be included in the README or .info file, then this would
 definitely lead to more work for the current SBo admins, who already put
 in a lot of time in maintaining SBo.  The fact is that many SlackBuild
 script maintainers are not that communicative (and I've been guilty of
 this myself -- I only just now got to updating OpenArena after /many/
 requests -- sorry!) and either the admins would have to try and track
 down all the maintainers to update their submissions to the new format
 or do it themselves.  And, of course, test the listed dependencies.
 What if someone forgot to add a dependency?  Each submission would have
 to be tested on a clean, newly installed system in a VM or something to
 ensure that the dependencies were listed correctly and in the right
 order.  That's a lot of work.


 I think this is both true and false. regarding the work load, you're
absolutely right, and I would be absolutely *delighted* to handle the
format-ensuring stuff. where you're dead wrong is the stuff about testing.
what in the world does all that have to do with anything? the testing
process wouldn't change one iota from where it currently stands.

 well, thanks to the folks who've made intelligent and well-thought out
points on both sides. hopefully we can get some maintainers to weight in
now. maintainers?

 thanks folks.

 J

 ___
 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 mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - 

Re: [Slackbuilds-users] VirtualBox Question

[JK Wood]

On May 24, 2012 12:18 PM, Rich Shepard rshep...@appl-ecosys.com wrote:

  The SBo page for VirtualBox notes that it will not build on a stock
x86_64
 system. What is meant by 'stock?' What's required to build it on a host
 running -13.37/x86_64?

 Rich

 ___
 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/


That means it requires the compat32 layer.  It still builds as 64 bit,
though.

JK
___
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] rsync dead?

[JK Wood]

On Sun, Mar 18, 2012 at 11:56 AM, B Watson yalh...@gmail.com wrote:

 On 3/18/12, Willy Sudiarto Raharjo will...@gmail.com wrote:
  Is it just me or is it true that the rsync in slackbuilds.org is not
  working?

 It works fine 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/


I know that for a while I was running with the old cardinal IP still in my
hosts file - you might check that.
___
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] Remove burp SlackBuild from pending

[JK Wood]

Not if it's in pending.
On Mar 16, 2012 10:10 PM, Arvydas Sidorenko asi...@gmail.com wrote:

 On Fri, Mar 16, 2012 at 11:03 AM, ABELA Chris chris.ab...@maltats.com
 wrote:
  Will you kindly remove my burp SlackBuild from pending? I overlooked
  something.
 
 
  ___
  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/
 

 You can do it yourself by going here: http://slackbuilds.org/remove/
 ___
 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 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] Remove burp SlackBuild from pending

[JK Wood]

On Sat, Mar 17, 2012 at 2:25 PM, Erik Hanson e...@slackbuilds.org wrote:

 On Sat, 17 Mar 2012 13:07:12 -0500
 JK Wood joshuakw...@gmail.com wrote:

  Not if it's in pending.
  
   You can do it yourself by going here: http://slackbuilds.org/remove/

 Yes, that link is to remove your submission from pending.

 --
 Erik Hanson
 ___
 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/


Whoops - I was thinking ready. Carry on.
___
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 libsigc++-2.2.9-i486-1_SBo.tgz

[JK Wood]

On Oct 28, 2011 4:47 PM, B Watson yalh...@gmail.com wrote:

 On 10/28/11, Graham Lawrence gl00...@gmail.com wrote:

  root@a:/usr/pkgs# updatedb
  root@a:/usr/pkgs# locate libsigc++-2*
  /usr/pkgs/libsigc++-2.2.9-i486-1_SBo.tgz

 This doesn't do what you expect. On UNIX and its kin, the shell does
 wildcard expansion before running commands. This means the * in your
 command was never seen by the locate command (instead, the shell
 expanded it to libsigc++-2.2.9-i486-1_SBo.tgz, and your command ran as
 locate libsigc++-2.2.9-i486-1_SBo.tgz). So it only found the package
 file (you were probably trying to locate the files installed by the
 package, not the actual package file itself...)

 One way to check whether libsigc++ is installed:

 $ ls /usr/lib/libsigc*.so
 /usr/lib/libsigc-2.0.so

 Another way:

 $ pkg-config --list-all|grep -i sigc
 sigc++-2.0  libsigc++ - Typesafe signal and callback
 system for C++

 (The pkg-config command, confusingly, has nothing to do with the
 slackware packaging system)

 When your nzbget ./configure script fails, look for a file called
 config.log, usually found in the same directory as the configure
 script. This will have the details (*lots* of details) on what the
 configure script did and why it failed. Try searching for sigc++ in that
 file (with less, or with a text editor).

 Another thing that happens fairly often with configure scripts: if
 the script fails because some library was missing, and you install the
 library and re-run the script in-place, it may fail again even though
 it shouldn't... because configure scripts can cache their results. Try
 completely deleting the nzbget-0.7.0 directory, untar it again, and
 start over.

 I just built nzbget-0.7.0 on 64-bit slackware 13.37 using the libsigc++
 and libpar2 from slackbuilds.org, and it built just fine. No way to test
 that it runs correctly though (I have no access to any nntp servers).
 ___
 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/


You can also view the package manifest:

$ less /var/log/packages/libsigc*

--JK
___
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] tangogps slackbuild doesn't work

[JK Wood]

On Sun, Aug 7, 2011 at 10:29 AM, Pierre Cazenave pwcazen...@gmail.comwrote:

 I'm sure you're aware, but just in case, there's sbopkg (
 http://www.sbopkg.org) which takes care of a lot of the mundane fetching,
 checking md5sums, checking signatures etc. for building packages from
 SlackBuilds.org. I honestly can't imagine building package for Slackware
 without it since it's queuing functionality means you can figure out the
 build order in a text file and then give it that queue file, set it running
 and forget about it until it's finished.

 Pierre



You can also edit each SlackBuild/.info file, which makes it fairly easy to
edit for upgrades, etc. The main thing this breaks is md5 calculation, but
you can force that to skip during the run as well.

--JK
___
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] nvidia-driver, nvidia-kernel

[JK Wood]

On Tue, Jun 21, 2011 at 8:13 PM, King Beowulf kingbeow...@gmail.com wrote:



 On Tue, Jun 21, 2011 at 8:36 AM, Robby Workman 
 rwork...@slackbuilds.orgwrote:

 On Tue, 21 Jun 2011 08:31:38 -0700
 King Beowulf kingbeow...@gmail.com wrote:

  Roberto brought to my attention that for both nvidia-driver and
  nvidia-kernel scripts the default should be
 
  SRCSUFFIX=nocompat32
 

 Please do.

 -RW


 nvidia-kernel.diff attached.  This should clear up some confusion.
 Hopefully...

 I sent in a spelling error diff for nvidia-driver yesterday.  Also,
 275.09.07 is out with new GPU support and KDE4 fixes.  If this is of
 interest to the community, I will hop right on it when I get home from this
 business trip.


 --
 You! What PLANET is this!
 -- McCoy, The City on the Edge of Forever, stardate 3134.0


 ___
 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/



I've always been under the impression that you can install with either
tarball, it's just a difference of whether you install the compat32 stuff.
When I run the installer manually, it specifically asks if you want to
install it. Perhaps there's a command-line flag that can be passed? This
would simplify things considerably.

--JK
___
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] GoogleEarth Won't Start

[JK Wood]

On Thu, Jun 16, 2011 at 2:55 PM, Rich Shepard rshep...@appl-ecosys.comwrote:

  Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for
 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the
 application.

  What I see on the virtual terminal is:

 /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such
 file or directory
 /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success

  Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the
 LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail.

  What might I have done wrong here?

 Rich
 ___
 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/


Is /opt/GoogleEarth/googleearth-bin executable?

--JK
___
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] SWIG? OpenOffice.org?

[JK Wood]

On Jun 15, 2011 2:48 PM, Rich Shepard rshep...@appl-ecosys.com wrote:

  There seems to be a few packages I use that no longer have build scripts
 in the repository. I built SWIG manually, and suppose I could run the OO.o
 rpm through rpm2tgz and see if I can install it after that.

  Are these pending (or removed) scripts going to be made available some
 time soon?

 Rich
 ___
 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/


If I remember correctly, SWIG is now in Slackware, and OO.o has been
deprecated in favor of LibreOffice.

-JK
___
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] Google Earth x86_64

[JK Wood]

On Fri, Jun 10, 2011 at 1:38 PM, King Beowulf kingbeow...@gmail.com wrote:

 Google provides a both x86 and x86_64 deb and rpm packages. The
 GoogleEarthLinux.bin script provided (version 6.0.3.2197 as of today, btw)
 is 32-bit only, and I can't seem to find a corresponding 64-bit version.
 (why can't Google provide a simple FTP accessible file list? Those damn
 fruitcakes...). It would be spiffy to recast the slackbuild script to allow
 a choice for the two flavors of Slackware.

 --
 You! What PLANET is this!
 -- McCoy, The City on the Edge of Forever, stardate 3134.0


 ___
 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/



The x86_64 packages are simply 32-bit packages reorganized for a multilib
system. There is no 64-bit Google Earth client.

--JK
___
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] BIOS Firmware Upgrade Kit

[JK Wood]

On Sun, Apr 3, 2011 at 1:28 PM, JK Wood joshuakw...@gmail.com wrote:



 On Sun, Apr 3, 2011 at 1:16 PM, Rich Shepard rshep...@appl-ecosys.comwrote:

 On Sun, 3 Apr 2011, JK Wood wrote:

  In any case, the Dell bios update tool, libsmbios, already exists on
 Slackbuilds.org, and works well.


 JK,

  I'll look more closely at this and contact Alan. The blurb on
 slackbuilds.org says it provides info on the BIOS, not that it will
 upgrade
 it. But, it may well be a starting point.

 Much thanks,

 Rich

 ___
 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/


 The functionality you're looking for is /usr/sbin/dellBiosUpdate-compat,
 and I can assure you it's there - I've used it several times to update my
 bios on this Dell Latitude D830.

 --JK


Also, see http://linux.dell.com/repo/firmware/bios-hdrs/ for the bios update
files themselves.

/usr/sbin/smbios-sys-info to grab your system tag (the dev_0x part of
the filename) and bios version

--JK
___
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] BIOS Firmware Upgrade Kit

[JK Wood]

Sorry for top-posting, blame the Android Gmail client.

In any case, the Dell bios update tool, libsmbios, already exists on
Slackbuilds.org, and works well.

--JK

On Apr 2, 2011 6:03 PM, Ivan Pavicevic ivan...@gmail.com wrote:

Rich,

I understand, and when I mentioned rpm2tgz, I assumed that it could be nice
starting point for firmware package dissection, and latter for repacking in
Slacware way.
I hope so that you'll soon find the answer and make a nice SB script. ;)

Ivan



On Sun, Apr 3, 2011 at 12:40 AM, Rich Shepard rshep...@appl-ecosys.com
wrote:

 On Sun, 3 Apr ...

-- 
If you don't care where you are, then you ain't lost

___
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 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] GConf and GORbit

[JK Wood]

On Thu, Mar 24, 2011 at 5:53 AM, Chris Abela chris.ab...@maltats.comwrote:



 The community does not deserve this. The Nazi reference is unwarranted and
 insults the memory of victims of dictatorship.



 Chris Abela




 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
___
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] Puppet (and more!) for Slackware

[JK Wood]

On Fri, Mar 18, 2011 at 12:01 PM, Marco Bonetti si...@slackware.it wrote:

 nice one, but I'd like to use something more system-specific


I'm usually against one-size-fits-all solutions, but rvm is the cleanest one
I've seen in a long time. Slackware handles Ruby in a far better way than
any other distro I've encountered, but rvm is still an extremely useful
tool.  I only wish it were provided such that packaging was a simple matter.

-JK
___
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] Maintainership

[JK Wood]

I'm pretty sure he meant thread not threat.

Also, OMG TOP POSTING (Sorry, blame the terrible Android gmail app for
that.)

On Oct 29, 2010 12:34 PM, Erik Hanson e...@slackbuilds.org wrote:

On Thu, 28 Oct 2010 18:07:33 -0500 Antonio Hernández Blas 
hba.nihilis...@gmail.com wrote:  On Th...
Certainly no threat was made. You quoted me and everyone can see that.

There is no new policy, I just want it to be easy for us admins to deal
with the lump of recently dropped scripts. I don't think I'm out of
line for asking that people do something that makes this a little bit
easier for us. Something as simple as submitting new maintainer info
now can reduce a lot of hassle later. While a maintainer may submit an
update once in a blue moon, we have to deal with submissions every day.
I'm sorry you don't understand that we have real lives as well.


--
Erik Hanson

___
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 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] portmidi

[JK Wood]

On Thursday, May 6, 2010, David Woodfall d...@unrealize.co.uk wrote:
 On (12:34 06/05/10), Tim King datim...@gmail.com put forth the proposition:

 Hi thanks for checking David.

 Yes I'm using the script from SBo for hydrogen and all depends including
 portmidi.  I AM using multilib as well (which I neglected to mention), but I
 am not using the 32 bit environment at all.  All of my build commands look
 like so:

 ARCH=x86_64 ./portmidi.SlackBuild

 Does all this need to be built 32 bit instead or is there something I need
 to do differently because of the multilib?


 I just built on x86_64 without problems, except I needed to edit the
 ladspa slackbuild.

 I really don't know if multilib will affect things. I would be
 inclined to think passing ARCH=x86_64 would just build as if it's
 plain x86_64.

 Perhaps someone else on the list will know more about that.



 Tim


Occasionally, you have to force it to use the correct libraries in a
multilib environment. SlackBuilds.org recommends
LDFLAGS=-L/usr/lib${LIBSUFFIX} but I invariably use
LDFLAGS=-L/lib${LIBSUFFIX} -L/usr/lib${LIBSUFFIX} in front of your
configure lines.

Otherwise, assuming you still have problems, you might want to look
for a Gentoo patch for multilib or something.

--JK
___
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] Please remove pending script for new release

[JK Wood]

On Tue, Jun 22, 2010 at 9:14 PM, Slacker build user 
slac...@slaphappygeeks.com wrote:

 Hi,

 I submitted a new build for bouml for the second time yesterday, today a
 new version was released.

 Could someone please remove it and I will submit the latest.

 (There is also a bouml_doc in pending but it remains the same).

 Three times is a charm, right?

 Thanks,

 Robert
 ___
 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/


Robert -

Perhaps it would be beneficial to test the new version for a few days in
order to make sure they haven't introduced new bugs?  Just a thought.

--JK
___
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] Updates - 20100613

[JK Wood]

On Sun, Jun 13, 2010 at 12:02 AM, Robby Workman rwork...@slackbuilds.orgwrote:


 games/ioquake3: Added (open source Quake 3 distribution)



ioquake3 already includes a SlackBuild in the source tarball, shipped by
upstream.  I sent in a patch a while back to enable multi-arch support which
I never heard back on, but otherwise it works just fine.  I don't know if
that has any bearing on its status in this repository, but wanted to add
that to the mix nonetheless.

-JK
___
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] portmidi

[JK Wood]

On Thursday, May 6, 2010, David Woodfall d...@unrealize.co.uk wrote:
 On (12:34 06/05/10), Tim King datim...@gmail.com put forth the proposition:

 Hi thanks for checking David.

 Yes I'm using the script from SBo for hydrogen and all depends including
 portmidi.  I AM using multilib as well (which I neglected to mention), but I
 am not using the 32 bit environment at all.  All of my build commands look
 like so:

 ARCH=x86_64 ./portmidi.SlackBuild

 Does all this need to be built 32 bit instead or is there something I need
 to do differently because of the multilib?


 I just built on x86_64 without problems, except I needed to edit the
 ladspa slackbuild.

 I really don't know if multilib will affect things. I would be
 inclined to think passing ARCH=x86_64 would just build as if it's
 plain x86_64.

 Perhaps someone else on the list will know more about that.



 Tim


Occasionally, you have to force it to use the correct libraries in a
multilib environment. SlackBuilds.org recommends
LDFLAGS=-L/usr/lib${LIBSUFFIX} but I invariably use
LDFLAGS=-L/lib${LIBSUFFIX} -L/usr/lib${LIBSUFFIX} in front of your
configure lines.

Otherwise, assuming you still have problems, you might want to look
for a Gentoo patch for multilib or something.

--JK
___
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] skype on sw 12.2

[JK Wood]

On Sat, Apr 24, 2010 at 9:46 AM, Greg' Ar Tourter artour...@gmail.comwrote:

 The most recent version of skype (2.1.0.x) work fine on both -13 and
 -current with the dynamic package (and on prior version of slack with
 the static package) but only if the binaries are not stripped.

 if you comment out the strip line in the slackbuilds,, and rebuild it
 will work fine. Otherwise, as you see it segfaults, no idea why.

 Hope this helps

 Cheers

 Greg

 On 24 April 2010 12:54, Eric Hameleers e...@alienbase.nl wrote:
  On Sat, 24 Apr 2010, wrodrigues wrote:
 
  On Sat, Apr 24, 2010 at 01:03:12PM +0700, Willy Sudiarto Raharjo wrote:
 
  The download link for skype 2.0.0.72 is broken. The later version of
  skype is skype_static-2.1.0.81 which compiles and installs on
 Slackware 12.2
  but gives Segmentation fault error when skype is run.
 
  I think it uses newer QT (4.4.0). That's why it would broke in 12.2
  Try the static version
 
 
  I tried the static version skype_static-2.1.0.81 which did not work.
  Unfortunately I am not able to get the earlier static version
  (skype_static-2.0.0.72)
 
  The slackbuild for skype from slackware 13 after compiling and
 installing
  gives the error skype: error while loading shared libraries:
  libQtDBus.so.4: cannot open shared object file: No such file or
 directory
  after launching. So I assume that I need to use slackbuilds from 12.2
 only.
 
  I still have a skype_static-2.0.0.72 tarball in my repository on
  http://slackware.com/~alien/slackbuilds/skype/build/http://slackware.com/%7Ealien/slackbuilds/skype/build/
 
  Eric
 
  --
  Eric Hameleers
  Email: al...@slackware.com
  Jabber: al...@jabber.xs4all.nl
  Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E  581E 5E56 AAAF A75C BDA0
 
  The two basic principles of Windows system administration:
  * For minor problems, reboot
  * For major problems, reinstall
  ___
  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 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/



This, a thousand times this.  I spent hours trying to get the newer one to
run, only to discover that it ran fine straight out of the tarball, but the
packaged version didn't.  I thought I'd found a bug in pkgtools, until I
realized that the md5 difference was thanks to strip.

--JK
___
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] wesnoth 1.8 slackware-current

[JK Wood]

In Wesnoth's defense, doing a release while trying to prepare for GSoC is
bound to result in some quirks.

--JK

On Apr 22, 2010 11:32 AM, Willy Sudiarto Raharjo will...@gmail.com
wrote:

 Thanks for the reply. As far as I can see you change the undefined 
png_error_ptr_NULL to NULL. S...
i believe it should have been fixed in their source, so you should see
them in the next release of Wesnoth (1.8.1)


--

Willy Sudiarto Raharjo Registered Linux User : 336579 Web :
http://www.informatix.or.id/willy Blog :...
___
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] libgnomeprintui

[JK Wood]

On Sat, Jun 27, 2009 at 3:43 PM, Chess Griffin ch...@chessgriffin.comwrote:

 * Niklas 'Nille' Åkerström nille.kun...@gmail.com [2009-06-27 22:37:27]:

  JK Wood wrote:
 
  Isn't gkt-doc in the linuxdoc-tools package?
  /Nille

 Yes, I believe so.

 --
 Chess Griffin

 ___
 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/




My bad.  Thanks guys!

--JK
___
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] libgnomeprintui

[JK Wood]

Hey all,

libgnomeprintui ships with --enable-gtk-doc=yes in the SlackBuild.
However, there is no gtk-doc build available at SBo, nor is it in
Slackware (unless I'm missing something obvious.)  This option should
be turned off, and left up to the user.

--JK
___
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] [REQ] Psi slackbuild

[JK Wood]

On Sun, Mar 22, 2009 at 6:25 PM, Xavier Maillard x...@gnu.org wrote:

 Hi,

 does anybody have a valid and working slackbuild for Psi (a
 jabber client) ? I am desperately trying to get it compiled here
 but I am miserabely failing in doing so :/

 Regards
Xavier
 --
 http://www.gnu.org
 http://www.april.org
 http://www.lolica.org
 ___
 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/


Psi requires QT 4 and QCA 2.  It won't build on Slackware 12.2 as-is.  The
required packages are in -current.  A submission of Psi to SBo would require
a package for QCA 2 (QT 4 is already available.)
http://psi-im.org/download/

--JK
___
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] Proposal of SBU marker in README's

[JK Wood]

On Thu, Feb 26, 2009 at 11:11 PM, Robby Workman rwork...@slackbuilds.orgwrote:

 On Thu, 26 Feb 2009 22:52:58 -0600
 Vincent Batts vba...@hashbangbash.com wrote:

  In the same fashion of the Linux-From-Scratch guide, what are
  everyone's idea on having a baseline package build time marked as the
  Single Build Unit (SBU). some package of consensus, and included in
  the README's could have in SBU's the relative build time of their
  SlackBuild. for example if libsndfile takes 4 minutes to build on
  your machine, that would be 1 SBU for you. therefore qt4 would be 45
  SBU's and ipcalc would be  1 SBU
 
  this is an idea that would provide more foresight to the prospective
  builders of any given SBo.


 Hrm, I don't know.

 On one hand, it would certainly be useful information to have, but at
 the same time, it's error prone -- either the data is very subjective
 (i.e. that took forever) or it requires the submitter to time every
 build they run and compare it against some standard build.

 Besides, something like this would take all the fun out of comparing
 build times -- there would be this boring 1SBU or 10SBU or
 400SBU instead of faster than a fifteen year old boy's first time
 with Eliza Dushku or this thing takes a metric assload of time to
 build

 -RW

 ___
 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/



I think that the metric buttload is a very useful unit of time when
expressing things like these.

--JK
___
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] VLC package?

[JK Wood]

On Tue, Feb 24, 2009 at 9:15 AM, Didier Spaier didier.spa...@epsm.frwrote:

 Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez écrit :
  Hello list,
 
  I don't see a VLC package on SBo...  Any chance of getting one?
 
  Thanks,
  Kevin
 

 Hello poster,

 I do not know, but you can find packages  SlackBuilds in Alien Bob's
 repositories, see 
 http://www.slackware.com/~alien/slackbuilds/http://www.slackware.com/%7Ealien/slackbuilds/

 Cheers,

 Didier
 ___
 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/


VLC is an utter monster to build on Slackware, with a horrid dependency
chain and a rather low chance of success.  Which is why alienBOB's build is
so important.  That's one of the few things that I'd rather go to him for
than SBo.  Read his SlackBuild to find out why.

--JK
___
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] sbopkg search tags

[JK Wood]

On Thu, Jan 29, 2009 at 7:52 PM, Phillip Warner pc_war...@yahoo.com wrote:

 The one feature sbopkg lacks that SlackBuilds.org has is the ability to
 search for packages based on search tags.

 Ideally, the search tags would be in the .info files.  I don't even
 remember what tags I used for all of my submissions, so I would not mind
 seeing them.  Perhaps a for loop and cat can just dump the tags at the end
 of the .info files in the repo, or all new submissions could start using
 them.

 Alternatively, perhaps all of the search tags could be listed in one file
 that sbopkg can grep.

 --phillip



 ___
 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/


AFAIK, there are no search tags in the .info files.  That's handled
internally at SBo, I don't know if they can be used externally.

-JK
___
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] Sbopkg 0.20.0 Released

[JK Wood]

On Tue, Jan 6, 2009 at 10:04 PM, Chess Griffin ch...@chessgriffin.comwrote:

 * JK Wood joshuakw...@gmail.com [2009-01-06 21:44:52]:

   Is this a reference to users having the same home directory for
 multiple
  installs, or the same /etc directory for multiple installs, or something?
  If you're running 12.1, you'll have a 12.1 environment.  You can't just
 tell
  it to build a package for a different version of Slackware, can you?
 

 No, nothing fancy like that.  I think there are some folks that just
 want to build different versions of apps in the different repos.  Many
 apps for 12.1 build ok for 12.2 and vice-versa.  There are some folks
 I know using the 12.2 repo for a 12.1 install but still need the 12.1
 install for items that are dependent on the slackware version.


 --
 Chess Griffin

 ___
 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/


 Ah, that makes more sense.  I'm with you now.

--JK
___
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] Updates - 20081210

[JK Wood]

On Thu, Dec 11, 2008 at 9:01 PM, Robby Workman rwork...@slackbuilds.orgwrote:

 On Thu, 11 Dec 2008 09:58:37 +0800
 Cherife Li cher...@dotimes.com wrote:

  So, how soon will the upload form be open?


 Give us a free weekend, okay? :)  As you are likely aware, several of
 the SlackBuilds.org admins are also Slackware team members, so we've
 been *really* working overtime recently, and a short break would be
 much appreciated

 -RW

 ___
 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/



Take all the time you guys need, please.  Not only do you deserve the break,
but it just may give me a chance to catch up some on my porting. =)
-JK
___
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] Freeze on New Submissions to Prepare for 12.2

[JK Wood]

Status of builds I maintain on -current:

driftnet - OK
___
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] Mirodi Snapshot Hosting

[JK Wood]

On Sun, Nov 23, 2008 at 1:25 PM, LukenShiro [EMAIL PROTECTED] wrote:

 sabato 22 novembre 2008, Robby Workman ha scritto:
  I don't see a reason why we can't host a svn snapshot.
  However, don't plan on making extremely frequent updates. :-)

 Hi,
  recently I've noticed serious problems in downloading some sources:
 - sourceforge mirrors often give timeouts;
 - some upstream projects believe to be smart changing web address from
 time to time, so some DOWNLOAD= lines are not valid anymore.
 - few of them use 'https://' so they cannot be downloaded with a simple
 'wget'.
 As soon as possible I intend to verify all package sources' availability
 to have a complete view, so I can tell which are related packages.

 I wonder if hosting some 'problematic' sources on slackbuilds.org (or on
 another correlative website), at least, would be workable.
  I suppose it is not possible to host _all_ of source files (as e.g.
 Gentoo does), to maintain continuity and to prevent broken links, is it?

 --
 GNU/Linux * Slackware 'current'
 GNU/Linux * Bluewhite64 'current'
 LU #210970 LM #98222 SU #12583

 ___
 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/


I thought the Sourceforge download problem was fixed, although I've noticed
the same thing recently.  Perhaps some SlackBuilds aren't using the proper
download link yet, but nobody's noticed to complain?
___
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] Ruby gems packaging policies

[JK Wood]

Anytime I've installed a gem, it handled the dependencies on its own.
That's built in to Ruby gems.

On Tue, Nov 18, 2008 at 8:42 AM, Marco Bonetti
[EMAIL PROTECTED]wrote:

 On Tue, November 18, 2008 15:22, Vincent Batts wrote:
  either that or just let gem do its own management, since it can keep up
  with versions/updates and dependency resolution for gems.
 yes, it's cool, but the problem arise since the gem is a dependency and
 not the final package :-/
 I'll experiment a little as soon as I get to my build machine.

 ciao

 --
 Marco Bonetti
 BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
 Slackintosh Linux Project Developer: http://workaround.ch/
 Linux-live http://workaround.ch/Linux-live for powerpc:
 http://workaround.ch/pub/rsync/mb/linux-live/
 My webstuff: http://sidbox.homelinux.org/

 My GnuPG key id: 0x86A91047

 ___
 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 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] Orphaned slackbuilds!

[JK Wood]

 --- On Wed, 11/12/08, Antonio Hernández Blas [EMAIL PROTECTED]
 wrote:

  From: Antonio Hernández Blas [EMAIL PROTECTED]
  Subject: [Slackbuilds-users] Orphaned slackbuilds!
  To: SlackBuilds.org Users List slackbuilds-users@slackbuilds.org
  Date: Wednesday, November 12, 2008, 11:41 PM
  Hi.
 
  Since i'm actually not using any of the next packages
  and also cause
  i'm focused in other things, i'm gonna stop to
  maintain them.
  I would apreciate if some SBo admin erase my
  data(MAINTAINER  EMAIL)
  in their info files ;-)
 
  desktop/kbfx
  desktop/wmii
  desktop/dmenu
  desktop/domino
  desktop/alphacube
  desktop/alltray
  desktop/linstasquared
  desktop/blended
  desktop/cylonminimal
  audio/faac
  audio/orpheus
  games/zsnes
  libraries/libixp
  libraries/DirectFB
  multimedia/mpeg2dec
  multimedia/kmplayer
  network/axel
  network/kmldonkey
  network/mldonkey
  office/oooqs2
  system/xf86-video-openchrome
  system/conky
  system/fglrx-driver
  system/fglrx-module
  libraries/libghttp
  multimedia/x264
  multimedia/ffmpeg
  office/lyx_qt4
 
  Sorry if this is an inconvenient but if someone can/want to
  mantain
  any of them, go ahead!
 
  btw, it seems like Heinz Wiesinger is working in ffmpeg and
  x264.
 
  In the other hand, i'm gonna be still maintaining the
  next ones :-)
 
  audio/cmus
  development/eclipse
  development/netbeans
  system/plan9port
  system/terminus-font
  system/efont-unicode-bdf
  system/montecarlo
  system/profont
 
  -hba
  ___
  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/



 I'm using xf86-video-openchrome on my Averatec, so I'll be happy to
maintain that.
___
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] fakeroot: missing source tarball

[JK Wood]

Well, if you have your own site, you could mirror the sources.  Or, you
could find some kind soul that would be willing to mirror for you.  I don't
know what the SBo policy is on that, although I'm sure that this case would
be up for some special consideration.  If you need someone to host as a
mirror, I'd be happy to do so.

On Sat, Jun 21, 2008 at 1:18 PM, Deak, Ferenc [EMAIL PROTECTED] wrote:

 On Sun, Jun 15, 2008 at 2:25 PM, Mauro Giachero
 [EMAIL PROTECTED] wrote:
  Hello Ferenc, slackers.
  I just noticed that the fakeroot source link is broken (the Debian
  guys removed the 1.9.4 tarball when releasing the 1.9.5).
  Unfortunately I don't have gcc on this box, so I'm unable to test
  whether the script as-is still works.

 Thanks, for the warning, I've uploaded the build script with the
 new version.

 By the way fakeroot is a little bit problematic, because the
 source of the old versions are always deleted from main site.
 If I follow the new release a few week later, plus there is a
 one week delay for accepting the new package than there
 always will be at least one month per year when the fakeroot
 package will be bad.
 Is there any solution for storing these kind of disappearing sources?


 feco
 ___
 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 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/