1 |
2008/11/19 Michael Moore <mikem.unet@×××××.com>: |
2 |
> On 17:59 Tue 18 Nov , Duncan wrote: |
3 |
>> Michael Moore <mikem.unet@×××××.com> posted |
4 |
>> 20081118170056.GC8575@×××××××.linwin, excerpted below, on Tue, 18 Nov |
5 |
>> 2008 22:30:56 +0530: |
6 |
>> |
7 |
>> > Indeed it doesn't. What i wanted to know was that can the bin package |
8 |
>> > provide the files needed for the softwares to compile against? If not, |
9 |
>> > then i guess i may have to stick with firefox lying around my sys. |
10 |
>> |
11 |
>> The -bin package will be 32-bit. 64-bit packages don't like 32-bit |
12 |
>> libraries. However, I'm not sure whether xulrunner is separately |
13 |
>> executable or works as a library. If it's executable, the 32-bit may be |
14 |
>> just fine. If it works as a library, no-go since that would be mixing 32- |
15 |
>> bit libs in 64-bit apps and that won't work. (FWIW xulrunner-1.9, for |
16 |
>> mozilla-firefox-3.x, has both binaries and shared-object libraries |
17 |
>> (.so*), but I'm not sure if the libraries are only used internally or |
18 |
>> not.) |
19 |
> |
20 |
> The wiki entry on xulrunner says:- |
21 |
> |
22 |
> "XULRunner is a runtime environment developed by the Mozilla Foundation for |
23 |
> providing a common back-end for XUL applications. It replaced the Gecko |
24 |
> Runtime Environment, a stalled project with a similar purpose." |
25 |
> ... |
26 |
> "Benefits of having a separate shared run-time environment are the same |
27 |
> as those with shared libraries. Benefits to developers and source-based |
28 |
> systems – that is, systems on which programs are compiled from source as |
29 |
> opposed to downloaded in binary form – are decreased compilation time, |
30 |
> less bandwidth needs and less storage space needed. Benefits for use on |
31 |
> binary-based systems are similarly less bandwidth and storage use." |
32 |
> |
33 |
> So, if i understand correctly, then, the -bin version can let the software |
34 |
> run but can't allow me to build it. So, acroread can work on top of |
35 |
> xulrunner-bin but can't be built (if Adobe someday open-sources it :-) ). |
36 |
> |
37 |
|
38 |
well, if xulrunner-bin would be built on amd64 then yes. but since |
39 |
it's built for 32bit then no. |
40 |
from the description you've made xulrunner is similar to a library and |
41 |
you cannot mix 32bit |
42 |
and 64bit libraries on the same machine at the same time. the reason |
43 |
for which you probably |
44 |
have both xulrunner and xulrunner-bin installed on a 64bit machine is |
45 |
multilib and |
46 |
apps like adobe reader that depends on xulrunner or seamonkey-bin. so your |
47 |
xulrunner-bin would be ok if you use a 32bit opera and 32bit |
48 |
gecko-mediaplayer but won't |
49 |
work if you use 64bit opera. |
50 |
|
51 |
>> FWIW, firefox-2 and the related gecko version is fast coming to the end |
52 |
>> of its mozilla support period. Any products depending on them that |
53 |
>> aren't already moving to newer gecko dependencies have a relatively short |
54 |
>> life expectancy at this point. Both thunderbird and seamonkey depend on |
55 |
>> them at present but have upgrades in the pipeline, altho there'll be a |
56 |
>> bit of a gap before full release. For thunderbird, there's arrangements |
57 |
>> already in place to cover the gap, but seamonkey and others are up in the |
58 |
>> air at this point. |
59 |
>> |
60 |
>> See the headlining feature article from the front page of the November 6, |
61 |
>> 2008 LWN weekly edition, here: |
62 |
>> |
63 |
>> November 6 LWN Weekly Edition front page: |
64 |
>> http://lwn.net/Articles/305169/ |
65 |
>> |
66 |
>> Article direct link: |
67 |
>> The end of the Road for Firefox 2 |
68 |
>> http://lwn.net/Articles/306015/ |
69 |
>> |
70 |
>> -- |
71 |
>> Duncan - List replies preferred. No HTML msgs. |
72 |
>> "Every nonfree program has a lord, a master -- |
73 |
>> and if you use the program, he is your master." Richard Stallman |
74 |
>> |
75 |
> |
76 |
> Interesting article, i had thought Mozilla would support the 2.x series |
77 |
> for a lot longer. |
78 |
|
79 |
there isn't any real reason for supporting the old 2 series since the |
80 |
new 3.0 has a lot of more features and better functions. supporting |
81 |
this old serie would only mean a waste of time to backport 3.0 |
82 |
features. |
83 |
|
84 |
-- |
85 |
dott. ing. beso |