[Bug 234495] Porters Handbook: Mention USE_GCC "currently" unconditionally sets gcc as a RUN_DEPENDS and show workaround

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Dec 30 01:44:29 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234495

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.freebsd.org/bu
                   |                            |gzilla/show_bug.cgi?id=2111
                   |                            |54
          Component|Individual Port(s)          |Documentation
             Status|New                         |Open
           Keywords|                            |easy, needs-patch
            Summary|USE_GCC installs gcc as a   |Porters Handbook: Mention
                   |run-depend?                 |USE_GCC "currently"
                   |                            |unconditionally sets gcc as
                   |                            |a RUN_DEPENDS and show
                   |                            |workaround
            Product|Ports & Packages            |Documentation
           Severity|Affects Only Me             |Affects Some People
                 CC|                            |gerald at FreeBSD.org,
                   |                            |ports-bugs at FreeBSD.org
           Assignee|ports-bugs at FreeBSD.org      |doc at FreeBSD.org

--- Comment #1 from Kubilay Kocak <koobs at FreeBSD.org> ---
Technically a documentation issue. The current documentation is not incorrect,
it is just not explicitly complete, mentioning also the fact that its a
RUN_DEPENDS too

The ability to specify gcc as a build *only* dependency is being handled in bug
211154, with workarounds in ports in the meantime taking the form of something
like ports r464059 (removing gcc from RUN_DEPENDS)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-doc mailing list