Use wildcards/glob patterns in flags

Bug #370811 reported by Sylvester Lykkehus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Smart Package Manager
New
Wishlist
Unassigned

Bug Description

Add the possibility to use wildcards when specifying flags.

Examples:
smart flag --set lock kernel-*
smart flag --set lock kde?-filelight

The idea came from using the zypper command on suse:
~>zypper help addlock
addlock (al) [options] <packagename> ...
Add a package lock. Specify packages to lock by exact name or by a glob pattern using '*' and '?' wildcard characters.

Revision history for this message
Anders F Björklund (afb) wrote :

Would those wildcard sapply a) at the command time when setting the flag or b) when matching the flag against packages later ?

tags: removed: flags glob lock wildcard
Changed in smart:
importance: Undecided → Wishlist
Revision history for this message
Sylvester Lykkehus (zly) wrote :

I would say, preferably when matching the flag against packages later.
Otherwise new packages would not be caught by the flag.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.