Re: Reading warnings when installing multiple ports

2009-05-19 Thread Mel Flynn
On Saturday 16 May 2009 21:21:54 Jerry McAllister wrote:
 On Sat, May 16, 2009 at 11:24:42AM +0200, Mel Flynn wrote:
  On Friday 15 May 2009 19:26:00 mfv wrote:
   On Tuesday 12 May 2009 13:53:35 Mel Flynn wrote:
On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:
 But, I very often wish there was a convenient way to see some of
 those messages and especially messages about things one has to do
 during the install, such as manually installing something or
 getting some license thing handled, before I start the port
 install.

 Sometimes I get a question in the middle of an install that I do
 not know how to answer and it is an awfully inconvenient time to
 have to start scrounging for information.Having a commannd that
 would display all those things and maybe some related information
 or pointers to information for making an intelligent response -
 before starting the make -  would be very helpful.
   
Do you have specific examples? Cause I can't think of anything that
falls under your description.
  
   Hello All,
  
   I had a recent experience with editors/openoffice.org-2.  Based on past
   experience I know that the compile would take a few hours.  I started
   make and left to do some chores.  When I returned I discovered that the
   program had aborted as I did not have java installed and had to
   download a patch from the Sun website.
 
  This can and will not ever be fixed, because it's a legal and not a
  technical issue.
  Once you know this, you know to install diablio-jdk first, which takes
  5-10 minutes pending download speed.

 Yes, I know it is a legal/license issue at Sun and I sort of know to do
 it now, having installed OO a couple of times.   But, the point was and is,
 it would help people if the information about having to do it would
 come up right at the first, so a person could have it taken care of
 instead of starting an install which one knows will take hours so
 leaves to do something else and comes back and finds the install
 stopped hours ago because of something that could have and should
 have been taken care of before actually starting the install.

JDK's should really set IS_INTERACTIVE if distfiles that are not available 
cannot be downloaded without user intervention (MAINTAINER cc'd because of 
this). This would signal portmaster to present you with a message before 
starting the build and letting you go about your business.

If your ports management software does not recurs through all configuration 
dialogs before starting the build, you're not using the right tool for the 
job.

 Some variation of this, often involving entering a 'y' or 'n' at
 some point in the middle of an install that could have been done
 causing an environmental variable or some such to be set ahead of
 time exists in a number of ports I have installed.   It is annoying
 to come back from a bunch of tiring meetings only to see that an
 install that could be finished has several more hours to run because
 it was waiting all that time for a y or n.

This is where -DBATCH comes in. It silences all those. The ones that aren't 
silenced and aren't legal issues, should be considered bugs. Various ports 
management tools also support automatic answer features. Without ports 
management software you can always run yes|make -DBATCH.

-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-19 Thread Jerry McAllister
On Tue, May 19, 2009 at 03:05:38PM +0200, Mel Flynn wrote:

 On Saturday 16 May 2009 21:21:54 Jerry McAllister wrote:
  Sometimes I get a question in the middle of an install that I do
  not know how to answer and it is an awfully inconvenient time to
  have to start scrounging for information.Having a commannd that
  would display all those things and maybe some related information
  or pointers to information for making an intelligent response -
  before starting the make -  would be very helpful.

 Do you have specific examples? Cause I can't think of anything that
 falls under your description.
   
Hello All,
   
I had a recent experience with editors/openoffice.org-2.  Based on past
experience I know that the compile would take a few hours.  I started
make and left to do some chores.  When I returned I discovered that the
program had aborted as I did not have java installed and had to
download a patch from the Sun website.
  
   This can and will not ever be fixed, because it's a legal and not a
   technical issue.
   Once you know this, you know to install diablio-jdk first, which takes
   5-10 minutes pending download speed.
 
  Yes, I know it is a legal/license issue at Sun and I sort of know to do
  it now, having installed OO a couple of times.   But, the point was and is,
  it would help people if the information about having to do it would
  come up right at the first, so a person could have it taken care of
  instead of starting an install which one knows will take hours so
  leaves to do something else and comes back and finds the install
  stopped hours ago because of something that could have and should
  have been taken care of before actually starting the install.
 
 JDK's should really set IS_INTERACTIVE if distfiles that are not available 
 cannot be downloaded without user intervention (MAINTAINER cc'd because of 
 this). This would signal portmaster to present you with a message before 
 starting the build and letting you go about your business.
 
 If your ports management software does not recurs through all configuration 
 dialogs before starting the build, you're not using the right tool for the 
 job.
 
  Some variation of this, often involving entering a 'y' or 'n' at
  some point in the middle of an install that could have been done
  causing an environmental variable or some such to be set ahead of
  time exists in a number of ports I have installed.   It is annoying
  to come back from a bunch of tiring meetings only to see that an
  install that could be finished has several more hours to run because
  it was waiting all that time for a y or n.
 
 This is where -DBATCH comes in. It silences all those. The ones that aren't 
 silenced and aren't legal issues, should be considered bugs. Various ports 
 management tools also support automatic answer features. Without ports 
 management software you can always run yes|make -DBATCH.

That is one thing to do, but, the answer is not absolutely always 'y'.   

Advanced information is still desirable.

jerry


 
 -- 
 Mel
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-16 Thread Mel Flynn
On Friday 15 May 2009 19:26:00 mfv wrote:
 On Tuesday 12 May 2009 13:53:35 Mel Flynn wrote:
  On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:
   But, I very often wish there was a convenient way to see some of those
   messages and especially messages about things one has to do during
   the install, such as manually installing something or getting some
   license thing handled, before I start the port install.
  
   Sometimes I get a question in the middle of an install that I do not
   know how to answer and it is an awfully inconvenient time to have
   to start scrounging for information.Having a commannd that
   would display all those things and maybe some related information
   or pointers to information for making an intelligent response - before
   starting the make -  would be very helpful.
 
  Do you have specific examples? Cause I can't think of anything that falls
  under your description.

 Hello All,

 I had a recent experience with editors/openoffice.org-2.  Based on past
 experience I know that the compile would take a few hours.  I started make
 and left to do some chores.  When I returned I discovered that the program
 had aborted as I did not have java installed and had to download a patch
 from the Sun website.

This can and will not ever be fixed, because it's a legal and not a technical 
issue.
Once you know this, you know to install diablio-jdk first, which takes 5-10 
minutes pending download speed.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-16 Thread Jerry McAllister
On Sat, May 16, 2009 at 11:24:42AM +0200, Mel Flynn wrote:

 On Friday 15 May 2009 19:26:00 mfv wrote:
  On Tuesday 12 May 2009 13:53:35 Mel Flynn wrote:
   On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:
But, I very often wish there was a convenient way to see some of those
messages and especially messages about things one has to do during
the install, such as manually installing something or getting some
license thing handled, before I start the port install.
   
Sometimes I get a question in the middle of an install that I do not
know how to answer and it is an awfully inconvenient time to have
to start scrounging for information.Having a commannd that
would display all those things and maybe some related information
or pointers to information for making an intelligent response - before
starting the make -  would be very helpful.
  
   Do you have specific examples? Cause I can't think of anything that falls
   under your description.
 
  Hello All,
 
  I had a recent experience with editors/openoffice.org-2.  Based on past
  experience I know that the compile would take a few hours.  I started make
  and left to do some chores.  When I returned I discovered that the program
  had aborted as I did not have java installed and had to download a patch
  from the Sun website.
 
 This can and will not ever be fixed, because it's a legal and not a technical 
 issue.
 Once you know this, you know to install diablio-jdk first, which takes 5-10 
 minutes pending download speed.

Yes, I know it is a legal/license issue at Sun and I sort of know to do 
it now, having installed OO a couple of times.   But, the point was and is,
it would help people if the information about having to do it would
come up right at the first, so a person could have it taken care of
instead of starting an install which one knows will take hours so
leaves to do something else and comes back and finds the install 
stopped hours ago because of something that could have and should
have been taken care of before actually starting the install.

Some variation of this, often involving entering a 'y' or 'n' at
some point in the middle of an install that could have been done
causing an environmental variable or some such to be set ahead of
time exists in a number of ports I have installed.   It is annoying
to come back from a bunch of tiring meetings only to see that an
install that could be finished has several more hours to run because
it was waiting all that time for a y or n.

Building that improvement into ports installs and some additional
why and wherefor information in the pkg-desc file or some other
useful and readily available place would help the ports system.
Of course, it would still be necessary to depend on the port
maintainer to provide these accurately and completely.

jerry
   
 -- 
 Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-15 Thread mfv
On Tuesday 12 May 2009 13:53:35 Mel Flynn wrote:
 On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:
  But, I very often wish there was a convenient way to see some of those
  messages and especially messages about things one has to do during
  the install, such as manually installing something or getting some
  license thing handled, before I start the port install.
 
  Sometimes I get a question in the middle of an install that I do not
  know how to answer and it is an awfully inconvenient time to have
  to start scrounging for information.Having a commannd that
  would display all those things and maybe some related information
  or pointers to information for making an intelligent response - before
  starting the make -  would be very helpful.

 Do you have specific examples? Cause I can't think of anything that falls
 under your description.

Hello All,

I had a recent experience with editors/openoffice.org-2.  Based on past 
experience I know that the compile would take a few hours.  I started make and 
left to do some chores.  When I returned I discovered that the program had  
aborted as I did not have java installed and had to download a patch from the 
Sun website.

I agree with Jerry about lining up all the necessary ducks so that an upgrade 
does not need constant attention.  Using portfetch -a -v  and portconfig -a 
-v  followed by portmaster -a -u -t -v does most of the work but some 
configure screens still pop up.

Cheers...

Marek


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-13 Thread Mel Flynn
On Tuesday 12 May 2009 21:04:57 Glen Barber wrote:
 On Tue, May 12, 2009 at 1:53 PM, Mel Flynn

 mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
  On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:
  But, I very often wish there was a convenient way to see some of those
  messages and especially messages about things one has to do during
  the install, such as manually installing something or getting some
  license thing handled, before I start the port install.
 
  Sometimes I get a question in the middle of an install that I do not
  know how to answer and it is an awfully inconvenient time to have
  to start scrounging for information.Having a commannd that
  would display all those things and maybe some related information
  or pointers to information for making an intelligent response - before
  starting the make -  would be very helpful.
 
  Do you have specific examples? Cause I can't think of anything that falls
  under your description.

 Perhaps he is talking about the 'make options' output, such as what is
 displayed right before x11-wm/fluxbox begins to build.  That is the
 only type of output I can ever remember seeing before a build begins.

Well, there's would you like to activate postfix in mailer.conf [y/n], but 
that never triggered me to scrounge for info and can be handled by -DBATCH and 
setting POSTFIX_DEFAULT_MTA in /etc/make.conf (or not setting it if you don't 
wanna).
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-12 Thread Mel Flynn
On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:

 But, I very often wish there was a convenient way to see some of those
 messages and especially messages about things one has to do during
 the install, such as manually installing something or getting some
 license thing handled, before I start the port install.

 Sometimes I get a question in the middle of an install that I do not
 know how to answer and it is an awfully inconvenient time to have
 to start scrounging for information.Having a commannd that
 would display all those things and maybe some related information
 or pointers to information for making an intelligent response - before
 starting the make -  would be very helpful.

Do you have specific examples? Cause I can't think of anything that falls 
under your description.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-12 Thread Glen Barber
On Tue, May 12, 2009 at 1:53 PM, Mel Flynn
mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
 On Monday 11 May 2009 15:21:24 Jerry McAllister wrote:

 But, I very often wish there was a convenient way to see some of those
 messages and especially messages about things one has to do during
 the install, such as manually installing something or getting some
 license thing handled, before I start the port install.

 Sometimes I get a question in the middle of an install that I do not
 know how to answer and it is an awfully inconvenient time to have
 to start scrounging for information.    Having a commannd that
 would display all those things and maybe some related information
 or pointers to information for making an intelligent response - before
 starting the make -  would be very helpful.

 Do you have specific examples? Cause I can't think of anything that falls
 under your description.

Perhaps he is talking about the 'make options' output, such as what is
displayed right before x11-wm/fluxbox begins to build.  That is the
only type of output I can ever remember seeing before a build begins.

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-11 Thread Jerry McAllister
On Sun, May 10, 2009 at 04:49:27PM -0700, Kelly Jones wrote:

 I often use make -DBATCH install to install ports.
 
 Problem: many ports spew out a warning/todo message after you install
 them (eg, you must manually create an x user or something).
 
 Since ports install recursively, I miss most of these messages.
 
 Can I tell ports to store these messages for me somewhere?
 
 Obviously, I can make -DBATCH install  /tmp/outfile, but that'll
 log all the install, test, etc commands that I don't want to see:
 I just want to see the warnings at the end of each install.

Check out   script(1)   It is not perfect, but it will put a copy
of everything in and out in to a file that you can peruse later.

There may be other ways, but this is easy.

jerry


 
 -- 
 We're just a Bunch Of Regular Guys, a collective group that's trying
 to understand and assimilate technology. We feel that resistance to
 new ideas and technology is unwise and ultimately futile.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-11 Thread Jerry McAllister
On Mon, May 11, 2009 at 06:52:39AM +0100, Matthew Seaman wrote:

 Kelly Jones wrote:
 I often use make -DBATCH install to install ports.
 
 Problem: many ports spew out a warning/todo message after you install
 them (eg, you must manually create an x user or something).
 
 Since ports install recursively, I miss most of these messages.
 
 Can I tell ports to store these messages for me somewhere?
 
 Obviously, I can make -DBATCH install  /tmp/outfile, but that'll
 log all the install, test, etc commands that I don't want to see:
 I just want to see the warnings at the end of each install.
 
 
 portmaster will save up package messages and display them all at the
 end of the session.  I believe a similar feature is planned for portupgrade
 but as far as I know it hasn't been released yet.

 
 In any case, you can redisplay the pkg-message for any installed port
 by:
 
   % pkg_info -Dx portname
 
   Cheers,
 
   Matthew
 

This is handy and seems to work.

But, I very often wish there was a convenient way to see some of those
messages and especially messages about things one has to do during
the install, such as manually installing something or getting some
license thing handled, before I start the port install.   

Sometimes I get a question in the middle of an install that I do not
know how to answer and it is an awfully inconvenient time to have
to start scrounging for information.Having a commannd that
would display all those things and maybe some related information
or pointers to information for making an intelligent response - before
starting the make -  would be very helpful.

jerry  

 
 -- 
 Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-10 Thread Glen Barber
On Sun, May 10, 2009 at 7:49 PM, Kelly Jones
kelly.terry.jo...@gmail.com wrote:
 I often use make -DBATCH install to install ports.

 Problem: many ports spew out a warning/todo message after you install
 them (eg, you must manually create an x user or something).

 Since ports install recursively, I miss most of these messages.

 Can I tell ports to store these messages for me somewhere?

 Obviously, I can make -DBATCH install  /tmp/outfile, but that'll
 log all the install, test, etc commands that I don't want to see:
 I just want to see the warnings at the end of each install.


Have a look at:
   /usr/ports/category/port/pkg-message

Some ports have the message output in the Makefile instead.

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Reading warnings when installing multiple ports

2009-05-10 Thread Matthew Seaman

Kelly Jones wrote:

I often use make -DBATCH install to install ports.

Problem: many ports spew out a warning/todo message after you install
them (eg, you must manually create an x user or something).

Since ports install recursively, I miss most of these messages.

Can I tell ports to store these messages for me somewhere?

Obviously, I can make -DBATCH install  /tmp/outfile, but that'll
log all the install, test, etc commands that I don't want to see:
I just want to see the warnings at the end of each install.



portmaster will save up package messages and display them all at the
end of the session.  I believe a similar feature is planned for portupgrade
but as far as I know it hasn't been released yet.

In any case, you can redisplay the pkg-message for any installed port
by:

  % pkg_info -Dx portname

Cheers,

Matthew


--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature