Hello,
At the moment the Xfce Panel Plugin packages in openSUSE follow the name of xfce4-panel-plugin-foo.
OTOH upstream and mainstream distributions all use xfce4-foo-plugin
This causes an issue of inconsistency with upstream and also search engines.
https://repology.org/project/xfce4-statusnotifier-plugin/versions
vs
https://repology.org/project/xfce4-statusnotifier-plugin/versions
I do not know the historical reason of such difference with upstream but would like to propose changing the package names following the upstream model instead. If there isn't any objection, I would like to start this renaming work with Xfce 4.14 which is to be released by August.
Best,
Am Tue, 2 Jul 2019 23:34:30 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
I do not know the historical reason of such difference with upstream but would like to propose changing the package names following the upstream model instead.
I do not know the reasons either, nor do I use those packages. But I wonder if it is really worth the hassle? I mean, the natural place to look for 3 dozen plugins is info provided by libzypp, not some webpage.
Olaf
On 7/2/19 11:47 PM, Olaf Hering wrote:
Am Tue, 2 Jul 2019 23:34:30 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
I do not know the historical reason of such difference with upstream but would like to propose changing the package names following the upstream model instead.
I do not know the reasons either, nor do I use those packages. But I wonder if it is really worth the hassle? I mean, the natural place to look for 3 dozen plugins is info provided by libzypp, not some webpage.
Olaf
libzypp only if a user is already using openSUSE. However for users who are not already on openSUSE and Xfce devs (as it happened) may not be clear immediately whether a plugin is included in the distribution. Ultimately it also helps us at Xfce openSUSE better keep track of things.
Long story short imo having a standard name policy is worth the "hassle" going forward to have a somewhat coherent ecosystem with both Xfce upstream and other distros.
Hi Maurizio,
Am 02.07.19 um 17:34 schrieb Maurizio Galli (MauG):
Hello,
At the moment the Xfce Panel Plugin packages in openSUSE follow the name of xfce4-panel-plugin-foo.
OTOH upstream and mainstream distributions all use xfce4-foo-plugin
This causes an issue of inconsistency with upstream and also search engines.
...> I do not know the historical reason of such difference with upstream but
Neither do I, it was already that way when I started maintaining xfce packages.
What I like about the current system, in the alphabetically sorted package list, all plugins are in the same place. But that's something not really important.
would like to propose changing the package names following the upstream model instead. If there isn't any objection, I would like to start this renaming work with Xfce 4.14 which is to be released by August.
I do not object. Just make sure that all packages have
# package was renamed in 2019 after Leap 15.1 Provides: xfce4-panel-plugin-foo = %{version} Obsoletes: xfce4-panel-plugin-foo < %{version}
...and keep it like that for the next 5 years or longer.
(Or maybe check docs / ask on opensuse-packaging@) what's the correct way to rename packages and still ensure that updates are working well, I'm not really an expert on that).
Have fun ;-)
Stefan
Hi Stefan, On 7/3/19 3:29 AM, Stefan Seyfried wrote:
I do not object. Just make sure that all packages have
# package was renamed in 2019 after Leap 15.1 Provides: xfce4-panel-plugin-foo = %{version} Obsoletes: xfce4-panel-plugin-foo < %{version}
...and keep it like that for the next 5 years or longer.
(Or maybe check docs / ask on opensuse-packaging@) what's the correct way to rename packages and still ensure that updates are working well, I'm not really an expert on that).
Yep will do so :). It will be tested in the xfce:next repo first as well when I get to it.
Am Thu, 4 Jul 2019 02:39:14 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
Provides: xfce4-panel-plugin-foo = %{version} Obsoletes: xfce4-panel-plugin-foo < %{version}
Also Obsolete the -debuginfo packages, nothing will swallow them during upgrade.
...and keep it like that for the next 5 years or longer.
Such knowledge has to stay forever in practice. These rpm tags cost nothing. The Wiki is wrong in this regard. Upgrade from any earlier release has to work every time.
Olaf
On 7/4/19 3:23 PM, Olaf Hering wrote:
Am Thu, 4 Jul 2019 02:39:14 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
Provides: xfce4-panel-plugin-foo = %{version} Obsoletes: xfce4-panel-plugin-foo < %{version}
Also Obsolete the -debuginfo packages, nothing will swallow them during upgrade.
...and keep it like that for the next 5 years or longer.
Such knowledge has to stay forever in practice. These rpm tags cost nothing. The Wiki is wrong in this regard. Upgrade from any earlier release has to work every time.
Olaf
Is it possible to add in the main package spec file? Because those packages are automatically created and I cannot find information on how to modify such debuginfo package.
Am Fri, 12 Jul 2019 15:04:10 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
Is it possible to add in the main package spec file?
That is how it needs to be done today. See cups-filters or NetworkManager-applet. There are surely many more renames that leave debuginfo behind.
Not sure how handle the -lang package. It requires the base version, so it already has an anchor. If the base version disappears there might be a conflict that must be resolved manually during 'zypper dup'. Just experiment yourself how a rename works in practice.
Olaf
On 7/12/19 3:22 PM, Olaf Hering wrote:
Am Fri, 12 Jul 2019 15:04:10 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
Is it possible to add in the main package spec file?
That is how it needs to be done today. See cups-filters or NetworkManager-applet. There are surely many more renames that leave debuginfo behind.
Not sure how handle the -lang package. It requires the base version, so it already has an anchor. If the base version disappears there might be a conflict that must be resolved manually during 'zypper dup'. Just experiment yourself how a rename works in practice.
Olaf
Thank you Olaf, I am not sure it's a good idea to add the provide/obsolete -lang package in the main spec.
If there no better way, I think for the lang package I will create manual subpackages adding the Obsoletes line instead of using the %lang_package macro:
MauG@openSUSE-LNX ~> rpm --eval %lang_package
%package lang Summary: Translations for package %{name} Group: System/Localization
Requires: %{name} = %{version}
Provides: %{name}-lang-all = %{version} Supplements: %{name} BuildArch: noarch %description lang Provides translations for the "%{name}" package.
On 7/12/19 3:22 PM, Olaf Hering wrote:
Am Fri, 12 Jul 2019 15:04:10 +0800 schrieb "Maurizio Galli (MauG)" mauriziogalli@opensuse.org:
Is it possible to add in the main package spec file?
That is how it needs to be done today. See cups-filters or NetworkManager-applet. There are surely many more renames that leave debuginfo behind.
Not sure how handle the -lang package. It requires the base version, so it already has an anchor. If the base version disappears there might be a conflict that must be resolved manually during 'zypper dup'. Just experiment yourself how a rename works in practice.
Olaf
From some practical tests I think I got it to work correctly. Old packages and lingering packages replaced/removed and new ones installed via 'dup'
https://build.opensuse.org/package/show/X11:xfce:next/xfce4-pulseaudio-plugi...
On 7/2/19 5:34 PM, Maurizio Galli (MauG) wrote:
https://repology.org/project/xfce4-statusnotifier-plugin/versions
vs
https://repology.org/project/xfce4-statusnotifier-plugin/versions
The 2 links are identical, unless I am missing something.
On Wed, 2019-07-03 at 11:43 +0200, Liam Proven wrote:
On 7/2/19 5:34 PM, Maurizio Galli (MauG) wrote:
https://repology.org/project/xfce4-statusnotifier-plugin/versions
vs
https://repology.org/project/xfce4-statusnotifier-plugin/versions
The 2 links are identical, unless I am missing something.
You're right, the second link should be:
https://repology.org/project/xfce4-panel-plugin-statusnotifier/versions
On 7/3/19 6:04 PM, Marcel Kühlhorn wrote:
On Wed, 2019-07-03 at 11:43 +0200, Liam Proven wrote:
On 7/2/19 5:34 PM, Maurizio Galli (MauG) wrote:
https://repology.org/project/xfce4-statusnotifier-plugin/versions
vs
https://repology.org/project/xfce4-statusnotifier-plugin/versions
The 2 links are identical, unless I am missing something.
You're right, the second link should be:
https://repology.org/project/xfce4-panel-plugin-statusnotifier/versions
Correct. My bad ;)
On Tue, Jul 2, 2019 at 11:34 PM Maurizio Galli (MauG) mauriziogalli@opensuse.org wrote:
Hello,
At the moment the Xfce Panel Plugin packages in openSUSE follow the name of xfce4-panel-plugin-foo.
OTOH upstream and mainstream distributions all use xfce4-foo-plugin
This causes an issue of inconsistency with upstream and also search engines.
https://repology.org/project/xfce4-statusnotifier-plugin/versions
vs
https://repology.org/project/xfce4-statusnotifier-plugin/versions
I do not know the historical reason of such difference with upstream but would like to propose changing the package names following the upstream model instead. If there isn't any objection, I would like to start this renaming work with Xfce 4.14 which is to be released by August.
Hello, Just an update on this, the panel plugins have been renamed and currently are in the X11:xfce:next repo [1]. If you're using that repo, a simple sudo zypper dup should automatically replace the plugin packages you have installed.
Please feel free to report issues. I'd like to start pushing the renamed packages to the current Xfce 4.12 in Factory first (making sure of compatibility) some time next week.
Cheers,
[1] https://build.opensuse.org/project/show/X11:xfce:next
-
Eion MacDonald -
Liam Proven -
Marcel Kühlhorn -
Maurizio Galli (MauG) -
Olaf Hering -
Stefan Seyfried