public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tero Grundström" <tero@vuosaari.hai.fi>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] thunderbird/firefox conflict
Date: Sat, 23 Jul 2005 17:02:56 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0507231645170.28996@vuosaari.hai.fi> (raw)
In-Reply-To: <42E2463A.1040903@planet.nl>

On Sat, 23 Jul 2005, Holly Bostick wrote:

> Benno Schulenberg schreef:
>> Holly Bostick wrote:
>>
>>> I understand heavy development, but three
>>> upgrades in three days is a bit much even for me
>>
>>
>> Come on, Holly, when you're running unstable (~x86), you've got to
>> be ready to take frequent updates.  Or, to circumvent this, you
>> could sync less often: once a week works fine here.
>
> In this case, syncing less often wasn't an issue-- the reason I had to
> upgrade to 1.0.6 was due to a GLSA.

I don't find any GLSA on firefox-1.0.6. Even the official firefox release
notes doesn't list any security fixes.

>>
>>
>>> (since it takes
>>> an hour and a half or so to compile each program, and further
>>> means I have to use Konq for that time if I don't want to mess up
>>> ff by having it loaded while it's upgrading.
>>
>>
>> There's no problem with using Firefox while it is being compiled.
>> Only as soon as it has actually been merged, it may be wise to
>> restart it.
>
>
> Not completely true. You can use an already-opened instance of
> Firefox--- as long as you stay within the same window.
>
> Open another window for any reason, and the whole thing will close down
> (because you can't open a new instance of Firefox while Firefox is
> compiling). So forums or database sites that open new windows to create
> posts, or display information about an item in the database are
> unuseable during this time.
>
> Rather than control my surfing, I prefer to use another browser until
> Firefox is finished compiling.

Erhm.. I don't know how in the world you could be seeing this kind of 
behavior while compiling firefox...

Anyways, you're just so wrong here, Holly (and Benno is right). Don't you
understand the concept of compiling? When something is being compiled
*nothing* gets installed during that time, and so it couldn't interfere
with your current installation. The program gets installed only after
compiling has finished.

make && make install, you know... or do you?

--
T.G.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-23 14:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23  3:31 [gentoo-user] thunderbird/firefox conflict Ryan Sims
2005-07-23  5:16 ` Patrick Rutkowski
2005-07-23  5:27   ` Zac Medico
2005-07-23 11:11     ` Holly Bostick
2005-07-23 12:44       ` Tero Grundström
2005-07-23 13:06         ` Holly Bostick
2005-07-23 13:15           ` Tero Grundström
2005-07-23 13:15       ` Benno Schulenberg
2005-07-23 13:29         ` Holly Bostick
2005-07-23 14:02           ` Tero Grundström [this message]
2005-07-23 14:23             ` Tero Grundström
2005-07-23 15:14             ` Holly Bostick
2005-07-23 15:49               ` Tero Grundström
2005-07-23 20:00                 ` Ryan Sims
2005-07-24 17:20       ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0507231645170.28996@vuosaari.hai.fi \
    --to=tero@vuosaari.hai.fi \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox