While I have no strong preferences for whether it would be better to allow
end-users determine what tags to apply as opposed to automatic system tags, it
might be more effective to make provisions for special tags to be supported in
info.rkt and have the catalog automatically read those tags if
All of your suggestions are great and get my vote.
To elaborate on the raco tag, it should list all the commands *and* subcommands.
Example:
pkg package
tag: raco: pkg install, pkg update, pkg remove, etc.
--
You received this message because you are subscribed to the Google Groups
"Racket
A `raco` tag for all packages that add raco commands is a great idea. I don't
think we should build some sort of system tag that's automatically added
though; I'd much rather have some way of granting "tagging rights" to a set of
catalog users and let them figure out what tags are appropriate fo
3 matches
Mail list logo
