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