Hi,
On 09-05-2025 17:19, Peter B wrote:
Circular dependencies, but does that matter?
Yes, they should be avoided.+1
I've moved the icon in other packages of mine before (I think WinFF, now team maintained here), to accommodate for the choice in AppStream to consider the package containing the icon to be the thing to install. II think we should add recommend: lazarus
don't like it, because the icon fits nicely in the -data package and I
had to create a "main" package to begin with IIRC, but I agree with the submitter that we should adapt to how the world works in this case.
</div><div><br></div><div>On 09-05-2025 17:19, Peter B wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Circular dependencies, but does that matter?<br></div></blockquote><div><br></before (I think WinFF, now <br></div><div>team maintained here), to accommodate for the choice in AppStream
<div><br></div><div>Yes, they should be avoided.<br></div></blockquote><div>+1</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>I've moved the icon in other packages of mine
I think we should add recommend: lazarus
On 09/05/2025 21:42, Abou Al Montacir wrote:
I think we should add recommend: lazarus
@Paul
Do you think we might get an RT unblock for this?
ISTM Significant benefit with minimal risk.
Maybe we should fix the following issue before https://appstream.debian.org/sid/main/issues/lazarus-ide-4.0.html
I would not worry about this for now. While the AppStream metainfo
file is recommended, it is not required. Valid metadata are
automatically generated from the desktop file (and other package data)
if the metainfo is not present.
(And there is no point in adding it now in my opinion since it needs
to be in the same package as the desktop file anyway).
Maybe we should fix the following issue before
https://appstream.debian.org/sid/main/issues/lazarus-ide-4.0.html
I also think about having two desktop files (Lazarus-gtk and
Lazarus-qt). This may be more relevant for GUI installer.
Let's not do anything until we agree on what should be done.
On 11/05/2025 09:05, Abou Al Montacir wrote:For now, only Gtk2 and Qt5 are compiled, so that limits the candidates.
I also think about having two desktop files (Lazarus-gtk and
Lazarus-qt). This may be more relevant for GUI installer.
Maybe for Forky. And maybe four. Gtk2, Gtk3, Qt5, Qt6
But I'd rather not go there for Trixie into the freeze.That's fair
I think Recommends is better as there is no strict requirement for this circularLet's not do anything until we agree on what should be done.
I was happy with your previous suggestion,
maybe like this?
Hi Abou,Looks good to me.
I've push the fix to Salsa.
Maybe its worth waiting the three days needed for version 4.0Yes, let's let it migrate first.
to migrate before uploading?
<div>I've push the fix to Salsa.<br></div></blockquote><div><div><span style="font-size: 14.666667px;">Looks good to me.</span></div></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></really installation on GUI. This can help us gain some time.</div><pre style="caret-color: rgb(46, 52, 54);
<div>Maybe its worth waiting the three days needed for version 4.0<br></div><div>to migrate before uploading?</div></blockquote><div>Yes, let's let it migrate first.</div><div><br></div><div>Maybe you can upload to experimental and test if this fixes
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 480 |
Nodes: | 16 (2 / 14) |
Uptime: | 252:20:19 |
Calls: | 9,532 |
Files: | 13,650 |
Messages: | 6,138,089 |