On 11.11.2016 01:49, Andrzej Telszewski wrote:
On 11/11/16 01:44, Willy Sudiarto Raharjo wrote:
The script checks whether python3 is available or not
if it does, it will add python3 build as well.
Exactly, but it's not mentioned in README.
The question is:
Should optional deps be mentioned i
On 11/11/16 01:07, David Spencer wrote:
Is there any way of being notified when one of the admins makes changes to a
package I maintain? I worry that not knowing about it, I might overwrite the
changes the admin made by re-using my version of the script (the version I
submitted and have on my co
It's extremely common for software development projects to mandate maximum
line lengths as part of their coding standards. I suggest that SBo picks a
number that would look good without X, in a console with a "vga"
framebuffer, and then demands that contributors follow it.
On Thursday, 10 November
Robbie / All --
Slight Mod to flashplayer-plugin.SlackBuild to allow ARCH=override on
multilib systems.
Tested on Slackware64 14.2 + Multilib.
Both ARCH=i386 and ARCH=x86_64 work fine ...
Not sure what would make sense but maybe a BLURB in the README would be
warranted as well ?
Thanks !
-- k
Thanks to all our contributors :)
Fri Nov 11 20:46:51 UTC 2016
academic/engauge: Fixed tarball handling.
academic/fet: Fixed download.
accessibility/xdotool: Update README.
audio/alsamodularsynth: Updated for version 2.1.2.
business/skrooge: updated for version 1.12.5.
desktop/i3: Updated for vers
On 11/11/16 09:35, Franzen wrote:
The question is:
Should optional deps be mentioned in README, also if they
are autodetected?
I feel: yes
Of course they should.
I read READMEs, but please don't make me read SlackBuilds to find out
optional packages.
When I posted this message, I thought the
On 11/11/16 22:23, David Spencer wrote:
development/dpkg: Updated for version 1.18.12.
The source code for dpkg 1.18.12:
http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz
seems to be missing on the server.
(it jumps from 1.18.10 -> 1.18.13)
--
Best regards,
Andrzej Telszewski
On 12/11/16 12:10, Andrzej Telszewski wrote:
> On 11/11/16 09:35, Franzen wrote:
>> The question is:
>> Should optional deps be mentioned in README, also if they
>> are autodetected?
>> I feel: yes
>
> Of course they should.
> I read READMEs, but please don't make me read SlackBuilds to find out
>
>> development/dpkg: Updated for version 1.18.12.
>
> The source code for dpkg 1.18.12:
> http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz
>
> seems to be missing on the server.
> (it jumps from 1.18.10 -> 1.18.13)
I guess they update faster than our public update :)
anyway i
Hi,
The source code for hunspell-pl 20160907 is missing upstream:
http://sjp.pl/slownik/ort/
It looks like they do not keep older versions.
It would be worth finding another mirror or hosting the source tarball.
(Bcc-d maintainer).
--
Best regards,
Andrzej Telszewski
__
On 12/11/16 00:54, Willy Sudiarto Raharjo wrote:
development/dpkg: Updated for version 1.18.12.
The source code for dpkg 1.18.12:
http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz
seems to be missing on the server.
(it jumps from 1.18.10 -> 1.18.13)
I guess they update fast
Thanks for B. Watson for his efforts updating most of the READMEs and
slack-desc'
For all maintainers, please make sure you grab the latest tarball or
SlackBuild script files from our website or repository before pushing an
update.
Sat Nov 12 00:00:09 UTC 2016
accessibility/Synkron: Update README
On 11/11/16, Willy Sudiarto Raharjo wrote:
> Thanks for B. Watson for his efforts updating most of the READMEs and
> slack-desc'
Actually that's only about half of the ones that need README updates,
more to come Real Soon Now.
___
SlackBuilds-users mai
13 matches
Mail list logo
