Date: Wed, 12 Dec 2018 22:03:37 +0100 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: Ian Lepore <ian@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: How much memory to compile www/chromium? Message-ID: <20181212210336.hlwwi3s7xy4qvtcl@squirrel.exwg.net> In-Reply-To: <1544646889.55242.8.camel@freebsd.org> References: <20181212165313.GA84881@www.zefox.net> <20181212184149.ol44fon2unowu35q@squirrel.exwg.net> <20181212192115.GA85583@www.zefox.net> <20181212202504.4n3mhtx7grbeh6j7@squirrel.exwg.net> <1544646889.55242.8.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
## Ian Lepore (ian@freebsd.org): > That's a bit of a harsh tone to take with a user who has questions. Sorry, the day is getting long (and it doesn't sound that harsh in german, it definitively wasn't meant that harsh). > If > Bob was an aspiring ports developer, maybe a response like that would > make some sense. Asking a user who knows how to build ports to be > poking around in and understanding the guts of the ports build > framework is a bit much. Asking them to even know bsd.port.mk *exists* > is a bit much. Every ports developer started by compiling their own ports :) At least, that's how I started. And I had mentioned bsd.ports.mk in my previous mail. > A good response would be to point a user to the manpage that documents > all this stuff. Oh wait... there isn't one. There is ports(7), and again it redirects to bsd.ports.mk. I'm not even sure we could have all the ports make variables in a man page - the knobs of the ports tree depend on your checkout (portsnap, svn, whatever) and not on the base system or some installed package. Regards, Christoph -- Spare Space.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181212210336.hlwwi3s7xy4qvtcl>