Hi Robert, I have a few remarks/questions.
The move implemented two different operations at once: 1. Grouping sysutils/fusefs-*, and removing the 'fusefs-' port prefix. 2. Grouping all filesystems-related ports. Old sysutils/fusefs-* ports now do not have the 'fusefs-' prefix, but the packages produced from them still have. Isn't that slightly confusing? That's maybe a non-existent case, but how would we handle a native driver vs. a FUSE implementation in ports, now that the latter are not prefixed? Is there a plan to tag the old sysutils/fusefs-* ports with, e.g., some 'fusefs' virtual category? That could come in handy when listing which FUSE filesystems are available (in particular with 'make search cat=fusefs'), even if there are other, though less user-friendly, ways to obtain this list. Thanks and regards. -- Olivier Certner
signature.asc
Description: This is a digitally signed message part.
