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 they are present. Developers and maintainers are already in a good position to furnish well chosen tags prior to uploading to pkgs.racket-lang.org.
On Monday, April 24, 2017 at 3:08:24 PM UTC-4, Jack Firth wrote: > 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 for the > variety of packages we have today. Not all sensible tags will have automatic > means of detection. Here's a sample list of tags I'd like to have used > consistently across the catalog: > > - raco: provides a raco command > - testing: provides something useful for testing code > - data: provides a data structure of some sort > ... -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
