Ricardo Wurmus <rek...@elephly.net> writes: > A good reason would be that the package *cannot* be used for anything > else (e.g. when it’s a custom variant of a library that would > otherwise be bundled but we decided to build it separately).
Ah, that's good to know for something else I'm packaging. :) > We hid “gcc” because users would install it instead of “gcc-toolchain” > and be surprised that it didn’t work. > > I would not hide a package just because it is a less popular > dependency of some more popular tool. Noted, thanks! Regards, Jakob
signature.asc
Description: PGP signature
