From: tink on
Hi Guys,

And sorry if this is the wrong place to ask this question; I've
been literally trying for months to get mozilla::mechanize
installed, searched perl-monks, google, google-groups
and the mozilla site for hours but seem to be too daft to
find any information that would tell me how I get the tools/libs
that comprise xpcom (and of course the file in the subject line!)
installed on my slackware machine.

Could someone point me at the starting point for this, or give
me a quick run-down of how to install this?

Cheers,
Tink
From: Robby Workman on
On 2008-01-31, tink <a.ricnik(a)gmail.com> wrote:
> Hi Guys,
>
> And sorry if this is the wrong place to ask this question; I've
> been literally trying for months to get mozilla::mechanize
> installed, searched perl-monks, google, google-groups
> and the mozilla site for hours but seem to be too daft to
> find any information that would tell me how I get the tools/libs
> that comprise xpcom (and of course the file in the subject line!)
> installed on my slackware machine.
>
> Could someone point me at the starting point for this, or give
> me a quick run-down of how to install this?


I have no experience with mozilla::mechanize, but I can tell you that
Slackware doesn't contain a 'mozilla-xpcom.pc' file. The seamonkey
package, however, does contain this:
/usr/lib/pkgconfig/seamonkey-xpcom.pc
Since Seamonkey *is* what used to be Mozilla, that's almost certainly
part of what you're trying to find.

If you need development libraries/headers for Mozilla, then Seamonkey
is definitely what you want. The Firefox and Thunderbird packages
that are shipped in Slackware are the official binary tarballs that
Mozilla.org releases (but the tarball contents are modified to live
in /usr as opposed to /usr/local, and a few *minor* patches for plugin
paths and such are applied) -- anyway, the point of noting that they
are the official binaries is that they do not contain the development
files (things that many distributions would package as "package-dev"
or some such.

-RW
From: Olive on
Robby Workman wrote:
> On 2008-01-31, tink <a.ricnik(a)gmail.com> wrote:
>> Hi Guys,
>>
>> And sorry if this is the wrong place to ask this question; I've
>> been literally trying for months to get mozilla::mechanize
>> installed, searched perl-monks, google, google-groups
>> and the mozilla site for hours but seem to be too daft to
>> find any information that would tell me how I get the tools/libs
>> that comprise xpcom (and of course the file in the subject line!)
>> installed on my slackware machine.
>>
>> Could someone point me at the starting point for this, or give
>> me a quick run-down of how to install this?
>
>
> I have no experience with mozilla::mechanize, but I can tell you that
> Slackware doesn't contain a 'mozilla-xpcom.pc' file. The seamonkey
> package, however, does contain this:
> /usr/lib/pkgconfig/seamonkey-xpcom.pc
> Since Seamonkey *is* what used to be Mozilla, that's almost certainly
> part of what you're trying to find.
>
> If you need development libraries/headers for Mozilla, then Seamonkey
> is definitely what you want.

But this is not exactly the same version as firefox; although they are a
great chance that this is compatible. I think the solution is to compile
firefox from source. This is actually quite easy and I do not understand
why Slackware does not do it.

Olive
From: Martijn Dekker on
In article <47a191c7$0$4836$bf4948fe(a)news.tele2.nl>,
Olive <notreal(a)noexist.org> wrote:

> [...] I think the solution is to compile
> firefox from source. This is actually quite easy and I do not understand
> why Slackware does not do it.

Because if they do, Slackware isn't allowed to call it Firefox or use
the Firefox icon.

- Martijn
From: Martijn Dekker on
In article
<987b653e-04fd-4e8a-bfaa-137b7609238d(a)m34g2000hsb.googlegroups.com>,
tink <a.ricnik(a)gmail.com> wrote:

> Could someone point me at the starting point for this, or give
> me a quick run-down of how to install this?

Mozilla is now called SeaMonkey. Install the seamonkey package, then
edit or patch your source to look for seamonkey-xpcom.pc instead of
mozilla-xpcom.pc. That should be all you need to change.

This command tells you where in the source to edit it:
grep -Rn 'seamonkey-xpcom\.pc' YOUR_SOURCE_DIRECTORY

- Martijn