<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi all, </p>
<p>I have started the update of Lazarus to version 3.0. Two points:<br>
</p>
<p>a) The package libqtpas requires to be updated to use Lazarus
3.0. I successfully contacted the maintainer Vijay Marcel which
will update libqtpas during this week.<br>
</p>
<p></p>
<p>b) Last December I tried to contact the doublecmd-qt5 package at
<a class="moz-txt-link-rfc2396E" href="mailto:no@no.noooo.ooo">"no@no.noooo.ooo"</a> and got no reply.</p>
<p> Since current doublecmd-qt breaks with Lazarus 3.0 which I've
updated today, I kindly <b>ask an SBo admin</b> to step in and
also update doublecmd-qt to the new version released today. I
submitted a proposal in the SBo site.<br>
</p>
<p> Current doublecmd-qt does not build on 32 bits as it needs a
reference to "i386". So my update proposal is:</p>
<p><br>
</p>
<p><font face="Courier New, Courier, monospace"><font size="2">diff
--unified doublecmd-qt5/doublecmd-qt5.SlackBuild
doublecmd-qt5.new/doublecmd-qt5.SlackBuild<br>
--- doublecmd-qt5/doublecmd-qt5.SlackBuild 2023-11-18
02:19:55.000000000 +0000<br>
+++ doublecmd-qt5.new/doublecmd-qt5.SlackBuild 2024-01-14
17:33:20.138867724 +0000<br>
@@ -25,7 +25,7 @@<br>
cd $(dirname $0) ; CWD=$(pwd)<br>
PRGNAM=doublecmd-qt5<br>
UPSTR_PRGNAME=doublecmd<br>
-VERSION=${VERSION:-1.0.11}<br>
+VERSION=${VERSION:-1.1.9}<br>
BUILD=${BUILD:-1}<br>
TAG=${TAG:-_SBo}<br>
OUTPUT=${OUTPUT:-/tmp}<br>
@@ -35,7 +35,7 @@<br>
<br>
if [ -z "$ARCH" ]; then<br>
case "$( uname -m )" in<br>
- i?86) ARCH=i586 ;;<br>
+ i?86) ARCH=i386 ;;<br>
arm*) ARCH=arm ;;<br>
*) ARCH=$( uname -m ) ;;<br>
esac<br>
@@ -46,7 +46,9 @@<br>
exit 0<br>
fi<br>
<br>
-if [ "$ARCH" = "i586" ]; then<br>
+if [ "$ARCH" = "i386" ]; then<br>
+ SLKLAZBUILDFLAGS="--cpu=i386"<br>
+elif [ "$ARCH" = "i586" ]; then<br>
SLKLAZBUILDFLAGS="--cpu=i586"<br>
elif [ "$ARCH" = "i686" ]; then<br>
SLKLAZBUILDFLAGS="--cpu=i686"<br>
@@ -65,6 +67,10 @@<br>
cd "$TMP/$PRGNAM-$VERSION"<br>
tar -zxvf "$CWD"/${UPSTR_PRGNAME}-$VERSION-src.tar.gz<br>
cd ${UPSTR_PRGNAME}-${VERSION}<br>
+<br>
+# 20240113 ALe: this symlink is mistargeted... removed<br>
+rm -rf doublecmd.app/Contents/MacOS/doublecmd<br>
+<br>
chown -R root:root .<br>
chmod -R u+w,go+r-w,a-s .<br>
find -L . \<br>
@@ -102,6 +108,7 @@<br>
# Gzip man page<br>
gzip $PKG/usr/man/man1/doublecmd.1<br>
<br>
+<br>
# Make package.<br>
mkdir -p $PKG/install<br>
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION<br>
diff --unified doublecmd-qt5/doublecmd-qt5.info
doublecmd-qt5.new/doublecmd-qt5.info<br>
--- doublecmd-qt5/doublecmd-qt5.info 2023-11-18
02:19:55.000000000 +0000<br>
+++ doublecmd-qt5.new/doublecmd-qt5.info 2024-01-14
17:26:36.888204475 +0000<br>
@@ -1,10 +1,10 @@<br>
PRGNAM="doublecmd-qt5"<br>
-VERSION="1.0.11"<br>
+VERSION="1.1.9"<br>
HOMEPAGE=<a class="moz-txt-link-rfc2396E" href="http://doublecmd.sourceforge.net/">"http://doublecmd.sourceforge.net/"</a><br>
-DOWNLOAD=<a class="moz-txt-link-rfc2396E" href="https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.0.11-src.tar.gz">"https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.0.11-src.tar.gz"</a><br>
-MD5SUM="f55d4fcfe1c3206a015cfb65e3936fed"<br>
+DOWNLOAD=<a class="moz-txt-link-rfc2396E" href="https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.1.9-src.tar.gz">"https://downloads.sourceforge.net/project/doublecmd/Double%20Commander%20Source/doublecmd-1.1.9-src.tar.gz"</a><br>
+MD5SUM="c7920140bc2f2cb17ca151e5d94eebeb"<br>
DOWNLOAD_x86_64=""<br>
MD5SUM_x86_64=""<br>
-REQUIRES="lazarus"<br>
+REQUIRES="lazarus libqtpas"<br>
MAINTAINER="Hao Chi Kiang"<br>
EMAIL=<a class="moz-txt-link-rfc2396E" href="mailto:no@no.noooo.ooo">"no@no.noooo.ooo"</a></font><br>
</font><br>
</p>
<p>Regards<br>
</p>
<p>António<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 26/12/23 23:54, Antonio Leal via
SlackBuilds-users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:988024fa-17f2-4770-8de6-706183ec3cb7@yahoo.com">Indeed I
could build both latest doublecmd-qt5 and winff with new Lazarus
directly from source.
<br>
<br>
But doublecmd-qt5 is in beta.
<br>
<br>
I contacted the maintainers so maybe an upgrade can be
coordinated.
<br>
<br>
Thanks for the help.
<br>
<br>
<br>
On 26/12/23 22:04, B. Watson wrote:
<br>
<blockquote type="cite">
<br>
<br>
Sorry this got so long & verbose, hopefully it'll be
helpful.
<br>
<br>
On Tue, 26 Dec 2023, Antonio Leal via SlackBuilds-users wrote:
<br>
<br>
<blockquote type="cite">So doublecmd-qt5 and winff don't build
with new Lazarus.
<br>
</blockquote>
<br>
Looks like doublecmd development moved from sourceforge to
github,
<br>
see <a class="moz-txt-link-freetext" href="https://github.com/doublecmd/doublecmd/releases">https://github.com/doublecmd/doublecmd/releases</a>
<br>
<br>
Possibly the latest 1.1.x release will build & work with
lazarus 3.0?
<br>
<br>
This would be a case where you coordinate with the maintainer.
However,
<br>
he's given his email address as <a class="moz-txt-link-rfc2396E" href="mailto:no@no.noooo.ooo">"no@no.noooo.ooo"</a> which doesn't
look like
<br>
a real address. Maybe he's subscribed to this mailing list, and
will see
<br>
this thread...?
<br>
<br>
For winff, there's also new releases. What we've got in our repo
is a random
<br>
git commit from September 2022. If you look here:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/WinFF/winff/tags">https://github.com/WinFF/winff/tags</a>
<br>
<br>
...you'll see that there have been several releases since
<br>
then. Perhaps the latest will work with lazarus 3.0. Here, the
SBo
<br>
maintainer is active and has a real email address, so you should
<br>
coordinate with him.
<br>
<br>
<blockquote type="cite">What is the SlackBuilds policy in this
situation?
<br>
<br>
a) Stay with current Lazarus 2.2.6 and hope that all packages
will eventually build correctly? Who keeps checking this and
how?
<br>
</blockquote>
<br>
You're the lazarus maintainer, so you check it... which you have
done,
<br>
and are doing. Also the maintainers of the other builds should
check.
<br>
<br>
<blockquote type="cite">b) Notify maintainers and upgrade
Lazarus to 3.0 anyway?
<br>
</blockquote>
<br>
Breaking peoples' builds by updating their dependencies is
<br>
rude. Notifying them that you're about to do it is slightly less
rude,
<br>
but it's still a hassle: puts pressure on the maintainer to drop
<br>
whatever else he's doing and fix his build (that wasn't broken
until
<br>
you broke it). Not a good way to treat unpaid volunteers...
<br>
<br>
<blockquote type="cite">c) Other?
<br>
</blockquote>
<br>
My preferred way of dealing with this situation is, I'd patch
<br>
the dependees (doublecmd-qt5 and winff), possibly updating them
<br>
to new versions. Get them working with the new lazarus. Then
send
<br>
the diffs to their builds (and lazarus) to the maintainers for
their
<br>
consideration. If they're OK with your changes, either they can
submit
<br>
the updates, or allow you to do it.
<br>
<br>
If you use github or some other public git repo, you can do it
as a
<br>
fork/branch. If you'd rather, you can just email the diffs (I'd
say
<br>
gzip them first). Since the doublecmd-qt5 maintainer's email
address
<br>
is bogus, I guess you have to mail the diffs to this mailing
list too.
<br>
If you do that, and we don't hear from him within some
reasonable
<br>
amount of time, most likely an SBo admin will step in and update
his
<br>
build.
<br>
</blockquote>
_______________________________________________
<br>
SlackBuilds-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
<br>
Archives -
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
<br>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>
<br>
<br>
</blockquote>
</body>
</html>