Package Details: vala-panel-git 24.05.r0.g295d892-1

Git Clone URL: https://aur.archlinux.org/vala-panel-git.git (read-only, click to copy)
Package Base: vala-panel-git
Description: Gtk3 panel for compositing window managers
Upstream URL: https://gitlab.com/vala-panel-project/vala-panel
Licenses: LGPL-3.0-or-later
Conflicts: vala-panel, vala-panel-sntray, vala-panel-sntray-git
Provides: vala-panel
Submitter: rilian
Maintainer: rilian
Last Packager: rilian
Votes: 23
Popularity: 0.054462
First Submitted: 2015-04-05 15:11 (UTC)
Last Updated: 2024-06-22 16:49 (UTC)

Dependencies (13)

Required by (15)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

rilian commented on 2023-12-20 10:10 (UTC)

@FabioLolix, @xiota AUR is capable to handling downgrade without epoch?

FabioLolix commented on 2023-10-23 05:52 (UTC)

@rilian pkgver= need to be the result of pkgver(), pleas don't past manually versions that don't exist

frankspace commented on 2023-10-22 23:31 (UTC)

I'm pretty sure the solution to the incorrect version number is to release a new epoch. So add epoch=1 to the PKGBUILD and then the actual correct version number (which would be 0.5.0.r18.gd197b89 as of the time I'm posting this).

Techman35 commented on 2023-10-07 06:55 (UTC)

The panel freeze when i add this applet :(

xiota commented on 2023-09-20 10:59 (UTC)

I did not tell you to write a merge request. Not seeing results in a search for merge requests is the reason I thought this was not a rename scenario.

I did not ask you to update "today". It is not urgent. Later this month or next would be fine. I will check back in a week or so. If the package is not updated, I will flag it as a reminder.

rilian commented on 2023-09-20 10:48 (UTC)

@xiota why I should write a merge request to myself?

About renames - I did this operation in that time with all of my multidesktop packages. If somebody want old package name - I will remove 'replaces' in all wanted names. But doing preemptively - not today. Maybe this month at least.

xiota commented on 2023-09-20 10:44 (UTC)

My mistake on the rename scenario. I searched for merge requests and didn't see any results.

The guideline is for future renames ("to be renamed"). The rename was long in the past, five years ago, so users have had plenty of time to install the new version.

rilian commented on 2023-09-20 10:38 (UTC)

@xiota For date of a rename, please see https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=vala-panel-sntray-git&id=2f2e1a168c051c934104b4a5c3474b0379e7cfd1

rilian commented on 2023-09-20 10:36 (UTC)

@xiota it was a rename scenario. When I wrote a PKGBUILD, I decided to store translations inside a 'vala-panel-sntray-translations' package. But next time I added gschemas to software, and decide to store gschemas alongside a translations. So, package 'vala-panel-sntray-translations' got renamed to 'vala-panel-sntray-common' and 'replaces' appeared. AFAIK, this is exactly a case of a replaces. Or I am wrong?

xiota commented on 2023-09-20 10:31 (UTC) (edited on 2023-09-20 10:32 (UTC) by xiota)

replaces forces users to use your package. The scenario you probably intend is for the other package to be removed when yours is installed. That is handled by conflicts. If your package can be used to satisfy dependencies, you should also add a provides.

As far as "forbidden", AUR submission guidelines state: Do not use replaces in an AUR PKGBUILD unless the package is to be renamed...

Since this is not a rename scenario, the guideline is clear that replaces is not to be used.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »