On Tuesday 26 May 2015 20:06:13 Christoph Willing wrote:
On 26/05/15 17:24, Christoph Willing wrote:
Hi Heinz,
Since you're updating the SlackBuild, I wonder if you would consider a
change to the way optional features are handled?
Unlike many other softwares, ffmpeg is quite good at
is it an option to have it autodetect if each of those libraries are
installed?
On Thu, May 28, 2015 at 12:12 PM, B Watson yalh...@gmail.com wrote:
On 5/28/15, Heinz Wiesinger ppr...@liwjatan.at wrote:
Leaving everything at no is the only sensible choice I'm afraid.
How about adding a
I pushed a different fix for this to github which should take care of it
properly.
Heh, that's much better!
I wondered if that would work but never tried it!! derp
Thanks
-D.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
On Thursday 28 May 2015 17:53:47 David Spencer wrote:
Hey folks,
Everything on the list is now building ok on 14.1 here, both x86_64
and i686, but -current needs more work.
The problems were fixed as follows:
[..]
multimedia/transcode -- needs lame in REQUIRES
I pushed a different fix
On Thursday 28 May 2015 16:56:55 Klaatu wrote:
Fellow SBo maintainers:
I have noticed that one of my own scripts depends on JACK, and that I
myself had listed the dependency as jack-audio-connection-kit.
Then I realised that this listing is not quite correct, because in fact
ANY package
On Tuesday 26 May 2015 03:51:44 B Watson wrote:
Another thing about building ffmpeg: it uses texi2html to generate the
developer documentation, and chokes if it can't find it in the $PATH
(usually because the user did plain 'su' instead of 'su -', or because
the T series isn't installed).
On 5/28/15, Heinz Wiesinger ppr...@liwjatan.at wrote:
Leaving everything at no is the only sensible choice I'm afraid.
How about adding a copy/pastable line to bottom of the README with all
the environment variables set to yes? Something like:
---cut---
To build with all optional dependencies,
On 5/28/15, Klaatu kla...@straightedgelinux.com wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
Kinda annoying if neither one is in REQUIRES in the .info file, it would
break sbotools or sqg's queue building.
2. re-structure the
On 05/28/2015 06:56 AM, Klaatu wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
or...
2. re-structure the jack-audio-connection-kit and jack2 scripts such
that they become one and the same script, by which the user can choose
to
On 05/28/2015 08:14 PM, David Spencer wrote:
2. re-structure the jack-audio-connection-kit and jack2 scripts such
that they become one and the same script, by which the user can choose
to build either jack1 or jack2, depending on their requirements.
What would be in DOWNLOAD= and VERSION=?
IMHO I don't see a reason to merge both into one SlackBuild.
I would say that JACK users are well aware that two versions exist and
this is also a decision from the upstream maintainers and those who
don't use JACK won't use it as it is may just a hard dependency from the
maintainer.
Also,
On 05/28/2015 06:54 PM, B Watson wrote:
On 5/28/15, Klaatu kla...@straightedgelinux.com wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
Kinda annoying if neither one is in REQUIRES in the .info file, it would
break sbotools or sqg's
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 Sudiarto Raharjo
2015-05-28 9:27 GMT+02:00 Charles char...@charlesmatkinson.org:
With regret, voluntary work as a Debian and (cough) Ubuntu sysadmin
leaves me no time to update the xapian-omega and yad SlackBuilds :(
I'll take yad, if nobody want it *badly*
Matteo
On Thu, 28 May 2015 22:05:51 +1200
Klaatu kla...@straightedgelinux.com wrote:
On 05/28/2015 08:14 PM, David Spencer wrote:
2. re-structure the jack-audio-connection-kit and jack2 scripts
such that they become one and the same script, by which the user
can choose to build either jack1 or
Just thinking out loud... You could have the separate scripts for jack1
and jack2 with their associated .info files set up as dependencies of
a jack-common (or whatever) build script which requires an argument to
select the version desired. Perhaps build information could be passed
via
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
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
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
On Friday 29 May 2015 01:55:44 Klaatu 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
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.
I would suggest put one of them as default dependency and list the other
one in README.
That's what i did with your aj-snapshot
2015-05-26 16:56 GMT+02:00 Willy Sudiarto Raharjo will...@slackbuilds.org:
Thanks, but what about the problem where it breaks the permissions on /tmp?
morticia# ls -ald /tmp/
drwxrwxrwt 25 root root 20480 May 26 15:23 /tmp/
here on my VM it gave different results
ls -l /tmp
drwx-- 2
Hey folks,
Everything on the list is now building ok on 14.1 here, both x86_64
and i686, but -current needs more work.
The problems were fixed as follows:
audio/audacity -- fixed with John V's patch
audio/mpd -- fixed with John V's upversion
games/alephone -- fixed with John V's patch on 14.1
sorry willy, I think David was referring to the permission of the /tmp
directory itself: from what I have understood it seem to overwrite the
normal permissions of 1777 with 0755...
Thanks Matteo, Willy and me sorted it out already, sorry for not
keeping the list up-to-date, but it was a bit
24 matches
Mail list logo
