Just spun up a different solution in my personal channel, creating a
package "gcc-unhidden" which inherits from the hidden gcc package and
uses (properties (alist-delete 'hidden?  (package-properties gcc))) to
expose it. If the standard use-case—what is expected for most
uses—doesn't require these libraries, maybe it would be better to create
a dedicated package for the edge cases that might need it?



(define-public gcc-unhidden
  (package
   (inherit gcc)
   (name "gcc-unhidden")
   (properties (alist-delete 'hidden? (package-properties gcc)))))

-- 
Christopher Rodriguez
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Attachment: signature.asc
Description: PGP signature

Reply via email to