Ports disconnected from category Makefiles
Ion-Mihai Tetcu
itetcu at people.tecnik93.com
Tue Aug 9 18:19:31 GMT 2005
On Tue, 9 Aug 2005 21:18:30 +0300
Ion-Mihai Tetcu <itetcu at people.tecnik93.com> wrote:
> On Tue, 9 Aug 2005 13:58:46 -0400
> Kris Kennaway <kris at obsecurity.org> wrote:
>
> > On Tue, Aug 09, 2005 at 08:55:22PM +0300, Ion-Mihai Tetcu wrote:
> > > On Tue, 09 Aug 2005 13:39:42 -0400
> > > Gregg Cooper <bsdcrank at squbes.com> wrote:
> > >
> > > > Kris Kennaway wrote:
> > > > >>... what is a "more better" way to snatch as many ports as
> > > > >>possible?
> > > > >
> > > > > Use make -k
> > > >
> > > > Excellent ... I was churning over in ports/Mk/bsd.port.mk
> > > > thinking it would hold the key and never even thought to go look
> > > > at make ... thanks!
> > >
> > > And if you really want to grab everything possible use:
> > > make -k -DDISABLE_VULNERABILITIES -DTRY_BROKEN
> > >
> > > It also might make sense to run a few parallel fetch jobs;
> > > especially on a slower/busy machine there's pretty much time spent
> > > "non-fetching".
> >
> > I was going to suggest this but you'll run the risk of collisions
> > between some of the ports that download the same distfiles, which
> > may lead to corruption.
>
> True; after the fetch is finished run a make checksum (this is a good
> idea for non-parallel fetch also).
With the same arguments, of course
make -k -DDISABLE_VULNERABILITIES -DTRY_BROKEN checksum
--
IOnut
Unregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
More information about the freebsd-ports
mailing list