Date: Wed, 12 Sep 2018 07:58:51 +0200 From: Matthias Fechner <idefix@fechner.net> To: freebsd-ports@freebsd.org Subject: Re: RUN_DEPENDS and portmaster Message-ID: <e1fb537a-1ee2-6409-2082-e1a11de04bc2@fechner.net> In-Reply-To: <7ccc8168-fa3b-9872-dc5a-13a9b394d5c2@freebsd.org> References: <03c14234-538d-fd9f-0c33-22825f3ea91d@fechner.net> <7ccc8168-fa3b-9872-dc5a-13a9b394d5c2@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Stefan, Dear Mathieu, Am 10.09.18 um 14:10 schrieb Stefan Esser: > This is a design decision in portmaster that has existed for at least > a decade. > > Use INSTALL_DEPENDS if you depend on a port being available and upgraded > before your port's do-install is invoked. > > Changing the current portmaster version in ports is no option, since it > does not offer to recursively upgrade or install any other port while > working on some port and it cannot easily be made to support such a > sequence of actions. thanks a lot for your explanation, so it seems to be a problem with portmaster. But as I do not want to block all users from using gitlab-ce that are using portmaster I think it is ok to define all RUN_DEPENDS also as BUILD_DEPENDS? I think this approach is already used by many ports... Gruß, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1fb537a-1ee2-6409-2082-e1a11de04bc2>