[Slackbuilds-users] Fwd: ocaml Slackbuild on SBo

[Shrivats]

Hi,

I sent this to the maintainer(also cc'd here)  a month back and there's no
response from them so far.

If there's no objection, can we please update the package to the latest,
with the attached patch that fixes build issues?

Shrivats

-- Forwarded message -
From: Shrivats 
Date: Sat, 3 Oct 2020, 10:23
Subject: ocaml Slackbuild on SBo
To: <>


Hi,

Hope this finds you well and safe - I noticed that the slackbuild for ocaml
<https://slackbuilds.org/repository/14.2/development/ocaml/> that has your
name listed as the maintainer is woefully out of date. So, I went ahead to
get it working on the latest 4.11.1 version of ocaml and I have attached
the diff here.

In summary:
* No more pre-build patching activity. Delete the .patch file
* CFLAGS didn't work correctly, it was failing while linking the assembly.
Pointed it directly to /usr/bin/as through the AS env var
* DESTDIR for building target packages for installs on other machines.

Would you be able to get it updated on SBo, please?

Shrivats
diff --git a/development/ocaml/configure.patch b/development/ocaml/configure.patch
deleted file mode 100644
index a57b19fb56..00
--- a/development/ocaml/configure.patch
+++ /dev/null
@@ -1,13 +0,0 @@
 configure_old	2014-05-23 22:45:22.0 +0200
-+++ configure	2014-05-23 22:45:31.0 +0200
-@@ -1612,6 +1612,10 @@
- nativecccompopts="$nativecccompopts -fomit-frame-pointer";;
- esac
- 
-+# Add additional flags from the environment
-+bytecccompopts="$bytecccompopts $CFLAGS"
-+nativecccompopts="$nativecccompopts $CFLAGS"
-+
- # Finish generated files
- 
- cclibs="$cclibs $mathlib"
diff --git a/development/ocaml/ocaml.SlackBuild b/development/ocaml/ocaml.SlackBuild
index 1f0ea4e709..f549290f92 100644
--- a/development/ocaml/ocaml.SlackBuild
+++ b/development/ocaml/ocaml.SlackBuild
@@ -24,7 +24,8 @@
 # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=ocaml
-VERSION=${VERSION:-4.03.0}
+VERSION=${VERSION:-4.11.1}
+DOC_VERSION=${DOC_VERSION:-4.11}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -70,17 +71,13 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-patch < $CWD/configure.patch
-
-CFLAGS="$SLKCFLAGS" ./configure \
-  --prefix /usr \
-  --libdir /usr/lib${LIBDIRSUFFIX}/ocaml \
-  --host $ARCH-slackware-linux
+AS=/usr/bin/as CFLAGS="$SLKCFLAGS" ./configure \
+  --prefix=/usr \
+  --libdir=/usr/lib${LIBDIRSUFFIX}/ocaml \
+  --host=$ARCH-slackware-linux
 
 make -j1 world.opt
-make -j1 install \
-  PREFIX=$PKG/usr \
-  LIBDIR=$PKG/usr/lib${LIBDIRSUFFIX}/ocaml
+make DESTDIR=$PKG -j1 install
 
 find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
@@ -90,7 +87,7 @@ find $PKG/usr/man -type f -exec gzip -9 {} \;
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
 cp -a Changes INSTALL* LICENSE README* VERSION \
   $PKG/usr/doc/$PRGNAM-$VERSION
-tar -xvf $CWD/ocaml-4.03-refman-html.tar.gz --no-same-owner -C $PKG/usr/doc/$PRGNAM-$VERSION/
+tar -xvf $CWD/ocaml-${DOC_VERSION}-refman-html.tar.gz --no-same-owner -C $PKG/usr/doc/$PRGNAM-$VERSION/
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install
diff --git a/development/ocaml/ocaml.info b/development/ocaml/ocaml.info
index 620db74149..6fdb2d5afa 100644
--- a/development/ocaml/ocaml.info
+++ b/development/ocaml/ocaml.info
@@ -1,10 +1,10 @@
 PRGNAM="ocaml"
-VERSION="4.03.0"
+VERSION="4.11.1"
 HOMEPAGE="http://caml.inria.fr;
-DOWNLOAD="http://caml.inria.fr/pub/distrib/ocaml-4.03/ocaml-4.03.0.tar.xz \
-  http://caml.inria.fr/pub/distrib/ocaml-4.03/ocaml-4.03-refman-html.tar.gz;
-MD5SUM="89f62881e03dfad0cf04991fbc03f955 \
-d3e44d3984d029d2e88ba219ad8e24c2"
+DOWNLOAD="http://caml.inria.fr/pub/distrib/ocaml-4.11/ocaml-4.11.1.tar.xz \
+  http://caml.inria.fr/pub/distrib/ocaml-4.11/ocaml-4.11-refman-html.tar.gz;
+MD5SUM="6cc5593468d6fe66dd49a76c6a975b66 \
+3f911185de1b8a71595b76c63a1fbea0"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
___
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] Strange problem with KeePass 2.39.1

[Shrivats]

Hey Thomas,

I pushed an update for version 2.40 and included KeePass.config.xml in this
update. It's currently in pending queue and you can try it out once it's
uploaded.

Sorry for the late reply.

Thanks,

Shrivats

On Fri, 15 Jun 2018 at 08:45, Thomas Szteliga  wrote:

> W dniu 15/06/2018 o 07:52, Shrivats pisze:
> > That may be true only if you download the binary release. But in the
> > SlackBuild, we use the Source release and I don't include
> > KeePass.config.xml in the package at all.
> > There are a couple things you can do as an user, if you don't prefer
> > keeping the config xml globally:
> > * Pass the path to your local configuration file through the command
> line
> > argument: '-cfg-local:' and override defaults.
> > * Keep your local configuration file in `~/.config/KeePass`
> > I'll think about including this file for global configuration (In the
> > source, it's `true` by default)
>
>
> Hello Shrivats,
>
> I did not use another binary, I used the source tarball
> provided in the .nfo file.
>
> I did some digging and now everything is clear, but I guess you'll
> need to somehow embed the XML in the Slackbuild.
>
> I tested this now, normally there is no
> `/usr/lib/KeePass/Release/KeePass.config.xml`
> after installation and normal usage, but if
> a user with write access to `/usr/lib/KeePass/Release/`
> runs KeePass once (for instance root) then this file is being
> created there (`/usr/lib/KeePass/Release/KeePass.config.xml`)
> and it has the problematic PreferUserConfiguration set to false
> and from this moment on KeePass will ignore all congiguration
> changes made by other users.
>
> Just give it a try and run KeePass as root once and then
> check if `/usr/lib/KeePass/Release/KeePass.config.xml`
> and if you're able save any configuration changes
> as a normal user.
>
>
> --
> Best regards
>
> Thomas Szteliga
>
>
___
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] Strange problem with KeePass 2.39.1

[Shrivats]

Hey,

That may be true only if you download the binary release. But in the
SlackBuild, we use the Source release and I don't include
KeePass.config.xml in the package at all.

There are a couple things you can do as an user, if you don't prefer
keeping the config xml globally:

* Pass the path to your local configuration file through the command line
argument: '-cfg-local:' and override defaults.
* Keep your local configuration file in `~/.config/KeePass`

I'll think about including this file for global configuration (In the
source, it's `true` by default)

Thanks,

Shrivats

On 14 June 2018 at 23:01, Thomas Szteliga  wrote:

> Hello,
>
> I've noticed a strange problem with KeePass.
> I see now in the description, that's the portable version.
> https://slackbuilds.org/repository/14.2/misc/KeePass/
>
>
> This version will not save user settings by default.
>
> So it won't remember the last opened file or any settings
> changed by a user without write permissions
> in /usr/lib/KeePass/Release/.
>
> The problem is caused by `PreferUserConfiguration`
> which is by default set to false in
> `/usr/lib/KeePass/Release/KeePass.config.xml`
>
>
> ~~~
> ...
> false
> ...
> ~~~
>
> Changing value to true will fix the problem and users
> will be able to have individual configs.
>
>
> Found this bit related:
> https://sourceforge.net/p/keepass/discussion/329221/thread/d8c595ac/
>
>
>
> --
> Best regards
>
> Thomas Szteliga
>
___
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] KeePass-2.38 installed in wrong directory

[Shrivats]

Heh, I thought that was fixed a while ago. Anyway, I'll take a look at it
tonight

Thanks for letting be know!

On Jan 30, 2018 11:31, "Thomas Szteliga"  wrote:

> Hello,
>
> is there a real reason why KeePass-2.38 is being installed
> in /usr/lib/KeePass-2.38  and not in /usr/lib/KeePass?
>
> AFAIR few months ago I've submitted a patch and this was corrected,
> but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.
>
> IMHO this is wrong, because this makes it harder to create packages
> for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
> the plugin Slackbuilds need to be upgraded too, even if the plugin
> was not changed. Plugins are compatible from one version to another,
> and they are "recompiled" (by KeePass) at runtime.
>
> I don't see any other program in /usr/lib/ which is installed
> to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.
>
>
> Can we maybe fix this once and for all? ;-)
>
>
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/20
> 16-August/016939.html
>
>
> --
> Thomas Szteliga
>
> ___
> 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] Whoops...

[Shrivats]

Ah, thanks! Didn't think of searching by email ID...

Shrivats

On 3 January 2018 at 20:39, Andreas Guldstrand <andreas.guldstr...@gmail.com
> wrote:

> On 3 January 2018 at 21:34, Shrivats <nast...@gmail.com> wrote:
> > For some odd reason, repology doesn't list him as a maintainer. Have we
> > taken all his repos off him?
> >
> > https://repology.org/maintainers/?search=Mello
> >
> > In any case, it'd be a good idea to list slack builds still up for grabs.
> >
>
> https://repology.org/maintainer/lmello.009%40gmail.com is the link
> which shows his builds
> ___
> 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] Whoops...

[Shrivats]

For some odd reason, repology doesn't list him as a maintainer. Have we
taken all his repos off him?

https://repology.org/maintainers/?search=Mello

In any case, it'd be a good idea to list slack builds still up for grabs.


Shrivats

On Jan 3, 2018 20:20, "B Watson" <yalh...@gmail.com> wrote:

> I got this mail from Luis Henrique Mello 3+ years ago and never got
> around to forwarding it to the list. Basically, all his SlackBuilds are
> up for grabs.
>
> -- Forwarded message --
> From: Luis Henrique Mello <lmello@gmail.com>
> Date: Sun, 14 Sep 2014 22:35:10 -0300
> Subject: Re: vamp-plugin-sdk
> To: B Watson <yalh...@gmail.com>
>
> Hi,
>
> My slack box simply 'died' :(
>
> It was quite a 'long' time, I recall sending a message to the mailing
> list about it before I signed out... anyway I'd would be proper to let
> everybody know that *all* my contributions to slackbuilds.org are freely
> available for anyone to do update and maintain them, since I cannot do
> that myself anymore.
>
> When I had my slack box working, there was something on the Submissions
> Guidelines about Public Domain. I see that has changed...
>
> Could you please forward this message?
>
> - Luis
>
> ps - I attached a simple 'ls' output from my slackbuilds backup folder,
> the last modification was from late 2013... yep that's around the time
> my old computer was still working. It could be of some use.
>
> On Sun, 2014-09-14 at 14:40 -0400, B Watson wrote:
> > Are you still maintaining vamp-plugin-sdk at SlackBuilds.org? I'm trying
> > to update my sonic-visualiser build, and it needs vamp-plugin-sdk 2.5.
> > The SBo repo has 2.4... upstream released 2.5 over a year ago, and
> > I've built it with your SlackBuild (just by setting VERSION=2.5 in the
> > environment).
> >
> > If you don't want to maintain the build, let me know. I'll be happy to
> > take over as maintainer, since my build depends on it.
>
> ___
> 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/

[Slackbuilds-users] SlackBuild version bumps on 14.1?

[Shrivats]

Hi,

I understand that 14.2 is on RC stage and we are all anxiously waiting
for it to be released. So, are we holding off on accepting new version
updates to existing SlackBuilds on SBo?

I have KeePass that requires a version update and I'm waiting to hear
back from someone before I go uploading it on SBo.

Shrivats
___
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] A couple notes on SBCL slackbuilds

[Shrivats]

Hi,

I managed to build SBCL on Slackware 14.1 and found a couple things that
can be mentioned on that SBo page.

* The slackbuild includes building pdf manuals. Building PDF requires
any variant of TeX installed. I turned it off and opted just for
building (emacs) info files.
* The SBo build(1.3.1) is not on the latest(1.3.5). The latest at
1.3.5 was released a few days ago[1]. However, that version is not
available from Sourceforge page, last I saw. So, I built 1.3.4
instead.

Can these be mentioned on SBo?

Shrivats

[1]: http://www.sbcl.org/news.html?1.3.5#1.3.5
___
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] Keepass and libgdiplus

[Shrivats]

Hi,

On 26 February 2015 at 06:23, Eric Pratt eric.b.pr...@gmail.com wrote:

 I have no issues with this.  Please take it over.  Thanks!

I have uploaded the package with newer version info and it's in
pending queue now.

If there's something wrong in the upload, please let me know.


Thanks,

Shrivats
___
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] Keepass and libgdiplus

[Shrivats]

Hi,

I recently built keepass on my slackware-14.1 machine and found that
the information present on the SBo is slightly wrong:

* It requires libgdiplus as a dependency [No mention on SBo]
* libgdiplus URL is wrong (Atleast, it didn't work for me when I tried
this morning - it should redirect to mono-project.com, which it never
did)

Apart from the above, both of them require a version bump:
Keepass - 2.28
libgdiplus - 3.12

Shrivats
___
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] Keepass and libgdiplus

[Shrivats]

Hi,

On 26 February 2015 at 01:30, Eric Pratt eric.b.pr...@gmail.com wrote:
 Actually, I don't use KeePass anymore so if anyone wants to take it
 over, please feel free.  If no one does, I'll try to submit a version
 bump for it soon (possibly as soon as this weekend.)

 About version dependencies, are we supposed to list dependencies of
 dependencies?  How many levels deep are we supposed to go?  I have
 only been mentioning one level of dependencies in my slackbuilds
 assuming people will follow the dependency tree.  If that's incorrect,
 I can definitely update my dependency lists.  But given that mono no
 longer requires libgdiplus, it will be a moot point for this
 slackbuild.


Normally we just list one level of dependencies - in this case, it
isn't a nested
level but an additional dependency to make KeePass work. IOW, libgdiplus
is a runtime dependency.

If you don't have any issues, perhaps I can take over maintenance?

Shrivats
___
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] Keepass and libgdiplus

[Shrivats]

Hi,

On 26 February 2015 at 01:32, Willy Sudiarto Raharjo
will...@slackbuilds.org wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Actually, I don't use KeePass anymore so if anyone wants to take
 it over, please feel free.  If no one does, I'll try to submit a
 version bump for it soon (possibly as soon as this weekend.)

 About version dependencies, are we supposed to list dependencies
 of dependencies?  How many levels deep are we supposed to go?  I
 have only been mentioning one level of dependencies in my
 slackbuilds assuming people will follow the dependency tree.  If
 that's incorrect, I can definitely update my dependency lists.  But
 given that mono no longer requires libgdiplus, it will be a moot
 point for this slackbuild.


 1 level of dependency
 I just tested that KeePass can be built without libgdiplus, but i
 didn't test for it's functionality. If it does require libgdiplus to
 be present in order for it to be functional, then yes, we can add
 libgdiplus to REQUIRES. Otherwise, leave mono as it's sole dependency


Although it's correct that KeePass doesn't require libgdiplus for it to build
successfully, it *does* require this library in order to run properly.

If Eric doesn't object, I can take over maintenance of this package.

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