Closed so1ve closed 2 years ago
If the search content does not contain @, it can be searched. If @ was added, a lot of extraneous stuff would appear and the manifest that was supposed to appear would disappear.
For example search: dvm@1. dvm@1.8.2 in so1ve/destiny_versions
should appear
If you're the bucket maintainer, I'd strongly suggest not using characters like @
, /
, \
for manifest names. These characters hold special meaning for Scoop and can unexpectedly break stuff.
@
is used for manually specifying a version while installation - if you want to denote version in manifest name, use a hyphen or underscore/
is used to specify the bucket prefix\
is used to specify the path for a local manifest fileHmmmm.... Can I use #?
You could try that, for reference see the following regex that captures package names:
Thanks!
I have deleted this bucket...I thought scoop didn't have the ability to install historical versions, I was wrong.
I created a scoop bucket called destiny_versions. It contains the historical versions of all the manifests in the destiny bucket. In order to distinguish it from other manifests, I added a special symbol "@" to the names of these manifests. However, the search engine does not seem to be able to search the manifest that includes these symbols.