From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] firefox and the latest git policy
Date: Wed, 09 Mar 2011 14:54:54 -0800 [thread overview]
Message-ID: <4D78053E.2030800@gmail.com> (raw)
In-Reply-To: <1299711161.6164.4.camel@tesla.lan>
On 03/09/2011 02:52 PM, Guido Trentalancia wrote:
> On Wed, 09/03/2011 at 14.24 -0800, Justin P. Mattock wrote:
>> On 03/09/2011 02:14 PM, Guido Trentalancia wrote:
>>> Have a look if this helps out (from Sven Vermeulen
>>> <sven.vermeulen@siphos.be>):
>>>
>>> [PATCH 05/15] Allow mozilla/firefox to manage tempfiles
>>> timestamped Wed, 9 Mar 2011 22:11:21 +0100
>>>
>>> firefox is not the most straightforward thing to build. Sometimes (not
>>> very often though) I ended up in an unusable build for example.
>>>
>>> Symptoms ? Logs ?
>>>
>>> It might also depend on the specific version, especially if it is a new
>>> one. Is 4.0 out ?
>>>
>>> Regards,
>>>
>>> Guido
>>>
>>
>> the version I am using is 3.6.13(did look at 4 but decided to just build
>> the stable version(which is outdated probably now))without xulrunner
>> being the main base for the lib*'s
>
> I had no problems running that version with refpolicy up to 15022011. If
> it is the latest stable version then I cannot see how that would be
> outdated. I suppose refpolicy is not based on unstable components.
>
> Regards,
>
> Guido
>
>
then its probably something over here that I need to look at on the
system(clfs)
Justin P. Mattock
next prev parent reply other threads:[~2011-03-09 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 21:30 [refpolicy] firefox and the latest git policy Justin P. Mattock
2011-03-09 21:43 ` Guido Trentalancia
2011-03-09 21:58 ` Justin P. Mattock
2011-03-09 22:14 ` Guido Trentalancia
2011-03-09 22:24 ` Justin P. Mattock
2011-03-09 22:52 ` Guido Trentalancia
2011-03-09 22:54 ` Justin P. Mattock [this message]
2011-03-11 20:01 ` Justin P. Mattock
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=4D78053E.2030800@gmail.com \
--to=justinmattock@gmail.com \
--cc=refpolicy@oss.tresys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.