You are not logged in.
'm not concerned about the name. I don't care what exact name will be. Razz
Of course new name won't change anything. It will be the same Firefox with patches from Arch devs, as always.
I agree. Changing name and logo imo will help to keep Mozilla people happy and AL out of trouble.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Now they are preparing 2.0 'mega-next-gen-release' which brings almost nothing new to be called 2.0.
Nothing new? It has a permanent Google talk back engine built into it. The worlds largest ad-ware company now has tracking software built into Firefox. I call that new.
Offline
Romashka wrote:Now they are preparing 2.0 'mega-next-gen-release' which brings almost nothing new to be called 2.0.
Nothing new? It has a permanent Google talk back engine built into it. The worlds largest ad-ware company now has tracking software built into Firefox. I call that new.
Are you talking about the tie-in to Google's anti-phishing service? They use the official google API and it looks fairly harmless. There has been a big push for browsers to have some kind of anti-phishing capabilities built in.
Offline
Romashka wrote:Now they are preparing 2.0 'mega-next-gen-release' which brings almost nothing new to be called 2.0.
Nothing new? It has a permanent Google talk back engine built into it. The worlds largest ad-ware company now has tracking software built into Firefox. I call that new.
wheeeee! hyperbolae! don't see how Google are an adware company, I can't think of any software they release containing ads. Websites dont count.
If it were a google talk back engine, and it had no method of disabling, I think we would have heard more. After all, Firefox is open source, so there's always a way to turn it off.
James
Offline
why use mozilla's stuff when there is much better available ??
what goes up must come down
Offline
why use mozilla's stuff when there is much better available ??
List the alternatives and if there's a package for ArchLinux.
Gruß, Johannes
http://www.hehejo.de
http://gallery.hehejo.de/jo
Offline
for web browsing : konqueror, epiphany, opera...
email client : kmail, evolution, sylpheed...
all of them are available trough arch.
i never liked thunderbird, and now kmail is very good. i used to use firefox but got bored of the way it renders some web pages + its general slowliness. konqueror does the job just fine. i only miss some (very few and barely used) extensions.
only a matter of 1) taste 2) trying something _slightly_ diferrent and changing a few habits.
what goes up must come down
Offline
I like thunderbird very much. And firefox renders nicer as opera (in my eyes).
But - why not wget the source and css and render by myself?
Gruß, Johannes
http://www.hehejo.de
http://gallery.hehejo.de/jo
Offline
for web browsing : konqueror, epiphany, opera...
1. KDE deps
2. GNOME deps
3. closed-source
Also, Epiphany is based on gecko, which is a mozilla product.
Offline
brazzmonkey wrote:for web browsing : konqueror, epiphany, opera...
1. KDE deps
2. GNOME deps
3. closed-source
Also, Epiphany is based on gecko, which is a mozilla product.
do you know another good Browser who is not closed source and have no KDE/GNOME Deps?
Have you tried to turn it off and on again?
Offline
I know all this about firefox is perhaps a drawback but how does it really affect Arch?
What do these patches do and is it that big a deal to get them approved by mozilla first?
Secondly would there not be a legal loophole for us that we could put the unpatched firefox in current and have the patches in community or something?
Intel i7-920 (stock), ASUS P6TD-Deluxe, AMD R9 270X, RAM: 6GB
Offline
do you know another good Browser who is not closed source and have no KDE/GNOME Deps?
Sadly, no. Maybe dillo, but it isn't as functional as all these browsers.
Offline
I know all this about firefox is perhaps a drawback but how does it really affect Arch?
What do these patches do and is it that big a deal to get them approved by mozilla first?
Secondly would there not be a legal loophole for us that we could put the unpatched firefox in current and have the patches in community or something?
I think you cannot just GET approval from Mozilla. It seems they are quite selective about what patches are approved. It also adds a new step to EACH new update to the firefox package. The simple solution is to just not using the firefox branding. I don't see why the branding is all that important to us (this is not Red Hat) using Arch Linux. If this was a commercial distro trying to sell a desktop product, we may want 'offical' for our distro.
Offline
Let's not get in to a complete tiz over the trademarks. Let's not forget about KDE(tm), GNOME(tm) and, gasp, Linux(tm) to name but three.
The browser market is clearly competitive in that all non-MS developers not only have to make a superior product (which they all generally do) but have to convert the mindsets of many users already familiar with something else, i.e., something a bit pants.
Mozilla is currently the only hope in giving IE some competition. I personally think it was a massive factor in IE7 not being just IE6+security patches. But let's not forget, Firefox is 100% open source! That's what FSF and all the OSI licenses are about: freeing the source. It's not about giving anyone control of the original product. It's not about doing what the OSS community wants, etc.
It makes perfect sense to protect themselves. If I patch Firefox, then I've created a deriviative work - it doesn't matter whether I've just merged a super-patch that makes it run 100% faster, be 100% secure or whatever. It's fair to assume that Firefox devs would eventually incorporate patches that make a positive impact in to their main source branch. However, until that point, that patched version is a fork and must be treated as such. It's also right to respect the requirements of the license that is letting you patch the source and redistribute.
Anyway, I'm off to create an ArchLinux fork. I think i'll switch to RPMs for starters. I think I'll remove pacman's dependency resolution. Might recompile everything under i386 to remove those i686 optimisations. Oh, but I think i'll still call it Arch Linux. That's ok, right?
Offline
@arooaroo: amen, i suppose.
I agree with this logic. As I stated above: why concern ourselves with branding. We could have an offical, unpatched firefox package and also a patched one. Say, mozilla-firefox and arch-browser (not a good name but you get the point) with which we could cannabalize/bastardize to our hearts content.
Offline
iBertus wrote:brazzmonkey wrote:for web browsing : konqueror, epiphany, opera...
1. KDE deps
2. GNOME deps
3. closed-source
Also, Epiphany is based on gecko, which is a mozilla product.do you know another good Browser who is not closed source and have no KDE/GNOME Deps?
Lynx FTW.
dogfin -
Offline
Lynx FTW.
Not practical for everyday usage. Lynx works fine for console-only systems or for working out of X, but lacks features that most want in a browser.
Offline
fk wrote:do you know another good Browser who is not closed source and have no KDE/GNOME Deps?
Sadly, no. Maybe dillo, but it isn't as functional as all these browsers.
Dillo has poor rendering engine, and I don't think it will improve much.
There is Gecko-based GTK2-only Kazehakase - it has not very good UI IMHO, but it works.
There is also GTK+ WebCore Project and few experimental browsers, for example Atlantis. Hovewer this project is not actively developed now.
I think all these are enought for browsing, if you don't want some fancy features, plugins etc.
Anyway most users have either GNOME or KDE libs installed, so I don't see the problem in using Epiphany or Konqueror for most of them.
to live is to die
Offline
It makes perfect sense to protect themselves. If I patch Firefox, then I've created a deriviative work - it doesn't matter whether I've just merged a super-patch that makes it run 100% faster, be 100% secure or whatever. It's fair to assume that Firefox devs would eventually incorporate patches that make a positive impact in to their main source branch. However, until that point, that patched version is a fork and must be treated as such. It's also right to respect the requirements of the license that is letting you patch the source and redistribute.
You do realize that patching and forking are different things?
to live is to die
Offline
You do realize that patching and forking are different things?
To the intents and purposes, they are the same thing. The motives may differ but ultimately they are both derivative works. A patched Firefox is not Firefox, nor is a forked Firefox.
Offline
Romashka wrote:You do realize that patching and forking are different things?
To the intents and purposes, they are the same thing. The motives may differ but ultimately they are both derivative works. A patched Firefox is not Firefox, nor is a forked Firefox.
This is much better formulation. I agree.
to live is to die
Offline
So, new names are chosen.
http://bbs.archlinux.org/viewtopic.php?t=25872
BTW, here is the bug report with all messages of MoCo-Debian conflict: http://bugs.debian.org/cgi-bin/bugrepor … bug=354622
to live is to die
Offline
From the GPL preamble...
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
..the way I see it is even RMS approves of MozCorp's actions...
charlie dont surf!
Offline
I am not sure if you have read this, but I think it contains some interesting information.
http://times.debian.net/1022-iceweasel
Offline
It makes perfect sense to protect themselves. If I patch Firefox, ...
I just wanted to say that arooaroo is my hero (for summing up my thoughts perfectly and thus saving me time), and that this:
We could have an offical, unpatched firefox package and also a patched one. Say, mozilla-firefox and arch-browser (not a good name but you get the point) with which we could cannabalize/bastardize to our hearts content.
seems like a great way for Arch to handle the issue, IF any changed need to be made at all.
Offline