Arch Linux

syn

Member

Registered: 2009-08-22

Posts: 43

A few questions about packaging policies.

I've done some googling and wiki'ing, but I can't seem to find the answers to these questions.

Why is it that Arch's Firefox package [pacman -Ss firefox] is labeled "Shiretoko" and doesn't use the Firefox icon. Another similar on is Thunderbird [pacman-Ss thunderbird].

On the subject of thunderbird, why is it that Arch, a bleeding edge distro doesn't have the 3.0 beta version packaged?

Any insight would be wonderful.

Pierre

Developer

From: Bonn

Registered: 2004-07-05

Posts: 1,967

Website

Re: A few questions about packaging policies.

We try to provide the latest stable versions; no beta/alpha whatever development releases.

---

3E80 CA1A 8B89 F69C BA57  D98A 76A5 EF90 5444 9A5C

ammon

Member

Registered: 2008-12-11

Posts: 413

Re: A few questions about packaging policies.

For betas/alfas we have AUR.

Mardoct

Member

Registered: 2009-08-17

Posts: 208

Re: A few questions about packaging policies.

What you get with a generic "pacman -S firefox" is the firefox realease 3.5, codenamed "Shiretoko". Their next realease, 3.6 codenamed "Namoroka" is due out within the next month or two.

---

The human being created civilization not because of willingness but of a need to be assimilated into higher orders of structure and meaning.

Garns

Member

Registered: 2008-05-28

Posts: 239

Re: A few questions about packaging policies.

Why is it that Arch's Firefox package [pacman -Ss firefox] is labeled "Shiretoko" and doesn't use the Firefox icon. Another similar on is Thunderbird [pacman-Ss thunderbird].

The Firefox package in Arch Linux is compiled without official branding. This means that when you start Firefox it will use a blue globe for its icon and will be named after its release series' codename. This has to be done because a distribution may use the name "Firefox" and its artwork only if there are no unofficial modifications (i.e. no custom patches).

ugkbunb

Member

Registered: 2009-02-26

Posts: 227

Re: A few questions about packaging policies.

To obtain the official branding search the forums for "firebrand" and/or "thunderbrand"... I believe IIRC there should be AUR packages for the two... just remember you will have to re-run them each time firefox or thunderbird is updated.

pyther

Member

Registered: 2008-01-21

Posts: 1,395

Website

Re: A few questions about packaging policies.

The reason why you do not see the official branding is because mozilla does not allow for distributions to distribute firefox with official branding if there are patches added to the vanilla sources. Since arch has a few patches to the firefox package, they can not package firefox with branding. It is okay to package firefox with official branding only if the arch devs were to get all patches approved from mozilla, but that would take an unnecessary amount of time.

---

Website - Blog - arch-home
Arch User since March 2005

MP2E

Member

Registered: 2009-09-05

Posts: 115

Re: A few questions about packaging policies.

To obtain the official branding search the forums for "firebrand" and/or "thunderbrand"... I believe IIRC there should be AUR packages for the two... just remember you will have to re-run them each time firefox or thunderbird is updated.

There is for firefox, look up the firefox-pgo package. It's what I use, also it includes faster javascript in x64

---

17:23 < ConSiGno> yeah baby I release the source code with your mom every night
17:24 < ConSiGno> you could call them nightly builds if you know what I mean

jamesbond007

Member

From: Germany

Registered: 2009-06-14

Posts: 150

Re: A few questions about packaging policies.

There is for firefox, look up the firefox-pgo package.

"firefox-pgo" - I read that many times on this forum. But I never found out what "pgo" stands for. Could someone please tell me?

Thanks in advance,
jamesbond007.

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,360

Re: A few questions about packaging policies.

Profile-guided optimization.

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

jamesbond007

Member

From: Germany

Registered: 2009-06-14

Posts: 150

Re: A few questions about packaging policies.

@ngoonee: thx!

mollison

Member

Registered: 2009-01-07

Posts: 15

Re: A few questions about packaging policies.

The reason why you do not see the official branding is because mozilla does not allow for distributions to distribute firefox with official branding if there are patches added to the vanilla sources. Since arch has a few patches to the firefox package, they can not package firefox with branding. It is okay to package firefox with official branding only if the arch devs were to get all patches approved from mozilla, but that would take an unnecessary amount of time.

May I ask, why does arch have patches to vanilla firefox? What do the patches do?

(Any replies to the effect of "go use ABS to figure it out yourself" will be met with "i have a LOT of homework"   but I admit, that is what I should do.)

Last edited by mollison (2009-10-04 06:01:20)

Nezmer

Member

Registered: 2008-10-24

Posts: 559

Website

Re: A few questions about packaging policies.

The reason why you do not see the official branding is because mozilla does not allow for distributions to distribute firefox with official branding if there are patches added to the vanilla sources. Since arch has a few patches to the firefox package, they can not package firefox with branding. It is okay to package firefox with official branding only if the arch devs were to get all patches approved from mozilla, but that would take an unnecessary amount of time.

May I ask, why does arch have patches to vanilla firefox? What do the patches do?

(Any replies to the effect of "go use ABS to figure it out yourself" will be met with "i have a LOT of homework"   but I admit, that is what I should do.)

I think If you build from source , the branding is disabled by default even without patches .

---

English is not my native language .

Beresford

Member

Registered: 2005-07-31

Posts: 23

Re: A few questions about packaging policies.

I'm also curious as to what gets patched with Firefox. I tried to have a look at the patch files, but couldn't really make sense of them, it looked like branding was being removed? Probably looking at the wrong place and lack of knowledge.

Last edited by Beresford (2009-10-12 02:41:35)

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: A few questions about packaging policies.

If anyone wants to see what Arch does to Firefox, all of the patches are available in the ABS tree or through the web interface.