Date: Tue, 13 Sep 2011 23:46:29 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Stephen Montgomery-Smith <stephen@missouri.edu> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, Gabor Kovesdan <gabor@freebsd.org>, Michal Varga <varga.michal@gmail.com> Subject: Re: Thank you (for making the ports less boring). Message-ID: <4E6FB315.804@yandex.ru> In-Reply-To: <4E6F46A3.4080809@missouri.edu> References: <1315864556.1747.103.camel@xenon> <20110912190558.641a3219@seibercom.net> <20110912230943.GD33455@guilt.hydra> <4E6E99BC.4050909@missouri.edu> <1315905051.1747.208.camel@xenon> <4E6F46A3.4080809@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen Montgomery-Smith wrote on 13.09.2011 16:03: > In particular, checking which ports depend on a port just updated is a > particularly nasty thing to do. I get the impression that each committer > has his own special way of doing this. For example, I have personally > found that a simple grep won't work, because "grep xxx > /usr/ports/*/Makefile*" just creates a line too long for the shell to > handle. I use a shell construction involving "find" but I wonder how > others do the same thing. http://beta.freshports.org/*category*/*portname* Required by: for Build for Run is quite useful as for me. But it can't catch all of them. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E6FB315.804>