New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x11-misc/slim : Upstream project forked, updated ebuilds #29838
Conversation
Pull request CI reportReport generated at: 2023-02-27 19:03 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Pull Request assignmentSubmitter: @RobPearce x11-misc/slim: @gentoo/proxy-maint (maintainer needed) Linked bugsBugs linked: 580458, 732430, 832303, 832562, 803476, 756181, 727544 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2023-02-28 18:58 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Would it help if I add myself as a proxy maintainer? I note that the Guide says to do so before committing the fixes but if I volunteer now, would that be OK? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your work on this, I see you closed a lot of bugs.
I didn't install and use this new slim yet, so I may come with further feedback after I do. It builds succesfully. I noticed 1.4.0 is missing a few files that still exist in 1.3.9 -
usr/share/slim/themes/original/{background.jpg,panel.png,slim.theme
. Is this intentional? Maybe upstream removed them?
Also - please squash your commits and then force push the changes. Ideally we should have 1 commit for 1.3.9 and one for 1.4.0, but having only one for both is also acceptable.
Thank you!
@@ -0,0 +1,47 @@ | |||
--- a/slim.conf.orig 2010-08-25 11:52:23.000000000 -0400 | |||
+++ b/slim.conf 2010-08-25 11:58:58.000000000 -0400 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the filename, it should be the same (probably a/slim.conf
and b/slim.conf
). Afterwards you can run scrub-patch files/slim-1.3.9-config.diff
to remove the timestamps. It will also output a few warnings, see if anything should be fixed or they can be ignored.
scrub-patch comes with app-portage/iwdevtools
.
Also please add a header to the patch file, i.e., where does it come from? What is it trying to fix? Maybe some relevant links.
Index: slim-fork-code/slim.conf | ||
=================================================================== | ||
--- slim-fork-code/slim.conf (revision 54) | ||
+++ slim-fork-code/slim.conf (working copy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is customary to prefix the files in the patch with a/
and b/
. For example a/slim.conf
. The patch is applied with -p1 by default, so it also works as it is, it's just a matter of style.
x11-misc/slim/metadata.xml
Outdated
@@ -3,6 +3,6 @@ | |||
<pkgmetadata> | |||
<!-- maintainer-needed --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please add yourself as a maintainer here if you are interested in maintaining this.
x11-misc/slim/slim-1.3.6-r5.ebuild
Outdated
@@ -20,7 +20,7 @@ RDEPEND="x11-libs/libXmu | |||
x11-libs/libXft | |||
x11-libs/libXrandr | |||
media-libs/libpng:0= | |||
virtual/jpeg:= | |||
media-libs/libjpeg-turbo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the stable ebuild. You cannot change RDEPEND without a revision bump, and bumping it would drop to unstable, so please don't change this ebuild, better wait until 1.3.9 (or 1.4.0) reaches stable and remove this old revision then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, fair point. I got carried away fixing pkgdev warnings
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
# Copyright 1999-2023 Gentoo Authors | ||
# Distributed under the terms of the GNU General Public License v2 | ||
|
||
EAPI=7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We try to bump all new ebuilds to EAPI 8.
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
} | ||
|
||
pkg_postinst() { | ||
# massage ${REPLACING_VERSIONS} to come up with whether or not it's a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.3.2 was removed from the tree in 2013, 10 years ago. Let's remove this check, it's long obsolete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth retaining (and, I note, fixing) the elog for a first install, or do you think that's superfluous? Ah, I see you mention this below. OK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also a pretty comprehensive (and slightly outdated) wiki page for SLIM: https://wiki.gentoo.org/wiki/SLiM so you can display a link instead or add it to that text.
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
@@ -0,0 +1,122 @@ | |||
# Copyright 1999-2023 Gentoo Authors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Short question - why is this ebuild named slim-1.3.9-r1.ebuild
? There was no -r0, you can start with slim-1.3.9.ebuild
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a 1.3.9 locally and posted it on the bugzilla (#832562) before spotting a fix that I felt was worth patching. As that ebuild had been made public and offered for inclusion in the tree, I wanted to avoid confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bugzilla attachments are irrelevant for portage ebuild revisions.
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
fi | ||
done | ||
|
||
if [[ ${rv} == none ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can use the readme.gentoo-r1
eclass to display a message only on first installation, to skip this none
check logic altogether.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this is optional - we can leave it for another time)
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
x11-libs/libXft | ||
x11-libs/libXrandr | ||
media-libs/libpng:0= | ||
media-libs/libjpeg-turbo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The dependencies should be sorted alphabetically. So please move media-libs/ deps upwards.
|
||
inherit cmake pam systemd | ||
|
||
if [[ ${PV} == "9999" ]] ; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no slim-9999.ebuild
, did you add one and forgot to push it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use one locally for testing - I'm not sure whether it would be desirable to add it. Which way would you prefer I fix this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add it and keep it in sync with the last version, no point in keeping it private since you already use it :)
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
x11-libs/libXft | ||
x11-libs/libXrandr | ||
media-libs/libpng:0= | ||
media-libs/libjpeg-turbo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
media-libs/libjpeg-turbo | |
media-libs/libjpeg-turbo:= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it necessary though? (I realise libjpeg-turbo has a subslot, but not every revdep links against specific soversion)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is linked against libjpeg.so.62
. So I guess if the 62 changes it will need rebuilding.
x11-misc/slim/slim-1.3.9-r1.ebuild
Outdated
IUSE="branding pam" | ||
|
||
RDEPEND="x11-libs/libXmu | ||
x11-libs/libX11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
x11-libs/libXext
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's only required for the "slimlock" tool, which is only built if PAM is enabled, so should this be
pam? (x11-libs/libXext)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. If it's used only with pam, add it conditionally.
I tried them both, they work. I like version 1.4 better, it has a nice green theme. |
Is it not the other way round? Upstream has a new default theme for 1.4.0 and those files are the old theme from 1.3.x retained for people who prefer pink to green. |
Right, I diffed them in reverse and got confused. Thanks for clarifying. |
Hopefully I've addressed all the issues and managed to squash the commits as requested. |
Pull request CI reportReport generated at: 2023-03-13 21:14 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only a few minor issues remain.
The commit message should start with x11-misc/slim:
, the prefix got lost while squashing. Also you lost all the Closes:
tags, please add them back.
Thank you!
x11-misc/slim/slim-1.3.9.ebuild
Outdated
|
||
EAPI=8 | ||
|
||
inherit cmake pam systemd readme.gentoo-r1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please sort inherits alphabetically (except when one eclass needs to be last, not the case here)
x11-misc/slim/slim-1.3.9.ebuild
Outdated
x11-libs/libXmu | ||
x11-libs/libX11 | ||
x11-libs/libXpm | ||
pam? ( x11-libs/libXext ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conditional dependencies go last. There is already a pam? ( ... )
below, please move x11-libs/libXext
there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rest of the dependencies need to be sorted too, for example x11-libs/libXft
comes before x11-libs/libXpm
, x11-apps/
before x11-libs/
and so on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, though it raises a separate question, which is a matter of preference, I think:
The pam USE flag currently controls whether slimlock is built. This follows the logic in the upstream CMakeLists from when Nobuhiro-san added it (at V1.3.6). That was, I think, an error - the slimlock code needs PAM and so should not be built without USE_PAM, but it's not required to build it because of PAM. This logic has changed upstream from V1.4.0 but I've retained the old behaviour through the ebuild. It might be considered better to introduce a different (package-specific) USE flag to control it, then encode that this USE flag needs USE=pam first. Of course, that would also be a change of behaviour, so might need a message, too... and I'm not sure it's really necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you see any value in building with pam
but without slimlock? Does slimlock require any extra dependencies, or does it take a long time to build? If not, no need to add an extra USE flag, tying slimlock to the same knob as pam sounds reasonable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think there's any real benefit other than "removal of cruft" (since I suspect very few people actually use slimlock). It adds only one dependency (libXext) but from the looks of things that's actually already an indirect dependency (via libXft?) and the build step for slimlock is pretty quick (one C++ file and a link).
So yes, the current approach feels pragmatically sensible.
x11-misc/slim/slim-1.3.9.ebuild
Outdated
} | ||
|
||
DISABLE_AUTOFORMATTING=1 | ||
DOC_CONTENTS=" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Global variables go before functions. Please move them above src_prepare
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, OK. Once again I copied this from an existing ebuild after searching for examples of the readme.gentoo-r1 eclass :(
Pull request CI reportReport generated at: 2023-03-14 08:44 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
It appears pkgcheck is unhappy your name in the GCO is different from the one in Author. Also the |
It looks like pkgcheck doesn't like |
No, it's ok. Your branch is older than the commit where But the name in the Signed-off-by line is still different from the one in Author. |
Fixed issues from pkgcheck List myself as a proxy maintainer Correct several issues pointed out in review by ceamac and added a -9999 ebuild in light of discussion Closes: https://bugs.gentoo.org/832562 Closes: https://bugs.gentoo.org/727544 Closes: https://bugs.gentoo.org/832303 Closes: https://bugs.gentoo.org/580458 Closes: https://bugs.gentoo.org/803476 Closes: https://bugs.gentoo.org/732430 Closes: https://bugs.gentoo.org/756181 Signed-off-by: Robert Pearce <gentoo@flitspace.org.uk>
Really? I was sure I'd changed it. Try now... |
Pull request CI reportReport generated at: 2023-03-14 18:44 UTC New issues caused by PR: There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
While trying to assign you the remaining bugs in bugzilla, it appears your bugzilla email is different from the one in Author and GCO. Please change it to be the same, so the automated tools work properly.
|
OK, will do. I see you found some old bugs I hadn't seen, so I'll look see if there's anything to be done. Although the one raised against a 2017 vintage -9999 ebuild may be tricky to follow up. |
Sorry, I meant the email in |
I thought I'd set that to match the bugzilla one. Having "bugs" in the commit author email wouldn't make sense but the docs said the metadata one needs to match the bugzilla login. |
Then we're good. Thank you! |
This pull request updates the Simple Login Manager to the latest release from the slim-fork project, which has resurrected what was a dead project and fixed lots of bugs.
Closes: https://bugs.gentoo.org/832562
Closes: https://bugs.gentoo.org/727544
Closes: https://bugs.gentoo.org/832303
Closes: https://bugs.gentoo.org/580458
Closes: https://bugs.gentoo.org/803476
Closes: https://bugs.gentoo.org/732430
Closes: https://bugs.gentoo.org/756181