You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I am experimenting with appstream-generator, I found the path structure inconvinient.
appstream-generator concat section and architecture. Which enforces the path section/architecture/os - and I found no way to customize this. In rpm world, we use just $section-$version-$arch. E.g. fedora-36-x86_64, fedora-rawhide-s390x.
I tried to workaround it by specifying . as architecture which resulted in fedora/./ which is a valid pathname for path fedora/ but appstream-generator fails to use such a path.
The text was updated successfully, but these errors were encountered:
Maybe we can make this configurable, or dependent on the use of the rpmmd backend... (but I wouldn't mind an extra configuration option for this at all, seems to be quite straightforward and easy to maintain).
It would probably make sense to make this fully configurable, because the Open Build Service generates "simple" debian repositories too, which would also benefit from being able to have their appstream data generated too.
As I am experimenting with appstream-generator, I found the path structure inconvinient.
appstream-generator concat
section
andarchitecture
. Which enforces the pathsection/architecture/os
- and I found no way to customize this. In rpm world, we use just$section-$version-$arch
. E.g.fedora-36-x86_64
,fedora-rawhide-s390x
.I tried to workaround it by specifying
.
as architecture which resulted infedora/./
which is a valid pathname for pathfedora/
but appstream-generator fails to use such a path.The text was updated successfully, but these errors were encountered: