<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
4. Re: Runports (root) Make Update (Solved) (Sander Holthaus)<br> 7. Re: Runports (root) Make Update (Solved) (Kris Moore)<br> ---------------------------------------------------------------------
<br>
Message: 4<br>
Date: Tue, 17 Mar 2009 16:37:16 +0100<br>
From: Sander Holthaus <<a href="mailto:info@2insite.nl">info@2insite.nl</a>><br>
<br>
On 17-3-2009 13:28, Ian Robinson wrote:<br>
> I attempted a few more times yesterday, each time stopping on ORBit2<br>
> part of the install.</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
The ports tree can "break" occasionally, usually because something is<br>
wrong with the dependencies or the ports-database is not up-to-date.<br>
</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 2. What exactly does the "make" command do? Does it compile a<br>
> database of ports or install certain key ports into the PCBSD ports tree?<br>
</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It depends where the make command is given and what the arguments are.<br>
Best read up on it in the FreeBSD handbook, while make is quite a simple<br>
command, the various arguments and uses make it a bit complex.<br>
><br>
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 4. What is up with the having to make numerous inputs at the blue<br>
> options screens -- that slows down the installation and requires the<br>
> user to sit for hours watching the install.<br>
</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Than you shouldn't use the ports tree / compile things. The reason<br>
people use ports instead of packages is that you can set all these<br>
options. You only need to do it once however. The ports tree is really<br>
meant for more advanced uses, for normal installs of ports, use packages<br>
(though I don't know how PCBSD deals with those).<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 17 Mar 2009 15:24:28 -0400<br>
From: Kris Moore <<a href="mailto:kris@pcbsd.com">kris@pcbsd.com</a>><br>
<br>
<br>
Sander Holthaus wrote:<br>
> On 17-3-2009 13:28, Ian Robinson wrote:<br>
>> I attempted a few more times yesterday, each time stopping on ORBit2<br>
>> part of the install.<br>
> The ports tree can "break" occasionally, usually because something is<br>
> wrong with the dependencies or the ports-database is not up-to-date.<br>
<br>
Thats right, often things in the ports tree are broken, so its best to<br>
update it often and see if that fixes the bug :)<br>
<br>
<br>
>> 4. What is up with the having to make numerous inputs at the blue<br>
>> options screens -- that slows down the installation and requires the<br>
>> user to sit for hours watching the install.<br>
> Than you shouldn't use the ports tree / compile things. The reason<br>
> people use ports instead of packages is that you can set all these<br>
> options. You only need to do it once however. The ports tree is really<br>
> meant for more advanced uses, for normal installs of ports, use packages<br>
> (though I don't know how PCBSD deals with those).<br>
<br>
Correct, also if you want to get rid of the blue options screen, edit<br>
/etc/make.conf and uncomment BATCH=yes, this makes it take all the<br>
defaults. Also through the "makeports" option, you can use pkg_add if<br>
you like at the same time. You'll want to refer to the FreeBSD docs for<br>
usage on this.<br>
<br>
--<br>
<br>
Kris Moore<br>
PC-BSD Software<br>
<a href="http://www.pcbsd.com" target="_blank">http://www.pcbsd.com</a><br>
<br>
<br>
------------------------------<br>
</blockquote></div><br><br>THANK YOU Sander and Kris.<br>
<br>
I update my ports tree frequently -- every couple of days -- and it
never ceases to amaze me how busy the ports committers are because of
the number of updates available each time. No matter how recently I
may have updated, I always update ports immediately before installing
anything from ports or before using portupgrade. Here, I upgraded each
time before working with runports. <br>
<br>
Perhaps the difference between success and failure was a day or two and
a broken port or its dependency on the first two tries. On the other
hand, perhaps runports would not complete because at some of the
screens I chose a couple of options other than the defaults. The
successful install was nothing but the defaults.<br>
<br>
Although I know what a makefile is and does, and in many cases, I can
read what's inside them effectively, what I did not know was where was
this global "make" coming from. It was not like I was in a ports
subdirectory running make install clean on the resident makefile. So,
I was referring not to makefiles in general, but to this one in
particular. Thank you Kris for the direction.<br>
<br>
It has only been lately (last several days) that I have ever recall
seeing the blue option screens while processing ports (other than using
sysinstall). At first I thought it was because 7.1 is in beta.
However, I was running portupgrade on one of my 1.5.1 installations and
I was seeing the option screen there too. I am grateful to know that I
can run unattended jumping past the defaults by tweaking /etc/make.conf.<br>
<br>
Kris -- Is the runports make because of the new arrangement separating
/usr/ports from PCBSD installed ports, and will all users have to
compile that after installation.<br>
<br>
Ian Robinson<br>
Salem, Ohio<br>