-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Labels
type::featurerequest for a new feature or capabilityrequest for a new feature or capability
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
Menuinst supports creating shortcuts for noarch packages (see this documentation), but it doesn’t appear to handle custom icons.
As we discussed during the transition to noarch (see this issue comment), we're unsure how custom icons are typically managed. Currently, we use bld.bat and build.sh scripts to copy the icon files to their final destination.
Is there a standard naming convention or another mechanism within menuinst that would allow us to automatically copy these icons without relying on custom build scripts?
Why is this needed?
building a noarch package with custom icons
What should happen?
by a naming convention for icons the icons get copied without a bld.bat or build.sh to the right directory. This should be documented.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
type::featurerequest for a new feature or capabilityrequest for a new feature or capability