/srv/irclogs.ubuntu.com/2008/11/24/#ubuntu-mozillateam.txt

fta_yep00:00
=== fta_ is now known as fta
mconnornspr_flags_by_pkg_config_hack00:00
mconnoris there an upstream bug, or a better explanation of what that's trying to fix?00:00
ftamconnor, it is needed because our tarball for firefox 3.0 is not full, it doesn't have nspr sources00:03
mconnoryou guys and your wacky tarball00:03
ftamconnor, the goal is to have less bits to upload, it's 10M vs 40M for the full one00:06
mconnorwhat all do you take out?00:06
mconnorthat seems like you're tossing a lot of code out of the tarball00:07
ftahold on00:07
mconnorI wish you could just point at the mozilla tarball + your patches... seems like it'd be saner than anything00:07
mconnoroh, yeah, are you guys pulling the know your rights patch in 3.0.5?00:08
ftahttp://bazaar.launchpad.net/~mozillateam/mozilla-devscripts/mozilla-devscripts/annotate/head:/src/mozclient/patches/xulbrowser_target.patch00:11
ftai guess, with 3.0.5, our know-your-rights patch will conflict so it will probably go away00:12
mconnoroh, right, because you build the app package separate from the xulrunner package00:12
mconnorit'll definitely conflict :)00:12
mconnorhmm00:14
mconnorthe don't depend on NSPR sources, couldn't you copy that file from the nspr location when building the source tarball?00:15
mconnorI'm mildly worried about us making changes to the original that you don't pick up00:16
ftaeverything is possible00:17
mconnoryeah00:17
mconnorI know00:17
mconnorI'm just treating this like I treat code reviews00:18
mconnorif there's a potential for stuff to go wrong, it will almost certainly go wrong00:18
ftathe point here is that when system nspr is requested, configure should not depend on the in-source version of nspr-config, even if it's in the tree, it may have diverged from the real system libs/headers00:18
mconnorfta: the patch means that configure depends on a specific version of make-system-wrappers.pl from the time of patch creation00:34
mconnorI'm not sure how that's better00:34
mconnormmm00:44
mconnorfta: what are the jemalloc patches doing?00:56
ftaare they still applied ?00:58
mconnoroh, I missed that they're commented out of the series patch01:00
mconnorok!01:00
mconnors/series patch/series file/01:00
ftai should clean that up01:01
mconnorbz436133_att322801.patch should be replaced with the patch that landed on 3.1 :P01:01
mconnorman, this default prefs patch is weird01:58
mconnoruh.05:52
mconnorfta / asac : I am confused by how/if part of one of these patches works...05:55
mconnoroh, nm05:57
mconnorman I hate this code05:57
asacmconnor: ok i am back from leave.09:57
asacmconnor: have to catch up on mail and stuff and then will focus on getting the patches upstreamed to bugs09:59
=== fta_ is now known as fta
asacfta: wanna take a look at one or two extensions from gnomefreak ;)10:51
asaci think he asked for a merge of firegpg10:51
asacand has two more new packages in pipeline10:51
asac@time14:38
ubottuCurrent time in Etc/UTC: November 24 2008, 14:38:22 - Next meeting: Server Team in 1 day14:38
asac@time central14:39
ubottuCurrent time in Canada/Central: November 24 2008, 08:39:01 - Next meeting: Server Team in 1 day14:39
asac@time US/central14:39
ubottuCurrent time in US/Central: November 24 2008, 08:39:08 - Next meeting: Server Team in 1 day14:39
asac@time14:59
ubottuCurrent time in Etc/UTC: November 24 2008, 14:59:21 - Next meeting: Server Team in 1 day14:59
mconnorasac: http://people.mozilla.com/~mconnor/trademark-review/Ubuntu/Round%201/16:20
mconnorasac: the "3.0 only" are stuff we have or should upstream16:21
mconnorthe "Needs Discssion" we should talk about :)16:21
[reed]mconnor: #16 is wrong on your list16:42
[reed]the prefs are in Firefox's prefs upstream16:42
[reed]not in Toolkit's16:43
[reed]that's the problem16:43
fta2damn, i can't send emails using my corporate address using thunderbird (or evolution), while i can with mutt.16:45
fta2smtp+auth with tb and evo, NOK. evo with sendmail, NOK. mutt with sendmail, OK.16:46
mconnor[reed]: mmm, I hate how that's split16:53
mconnorwe need that toolkit prefs file16:53
[reed]you just hate XULRunner16:54
[reed];)16:54
mconnorI hate that its something everyone's hacking around stuff16:55
[reed]instead of filing upstream?16:55
[reed]I agree with you there16:55
mconnorit made me sad that only like 1/3 of things were filed16:55
mconnorand that you'd been the one to file them :_/16:55
mconnorI mean, this is like 18 months of not bothering...16:56
mconnoras for 16, well16:57
mconnordoes it need its own prefs file?16:57
mconnorbecause, well16:57
[reed]yeah16:57
[reed]well16:57
[reed]we should split out anything in toolkit to a separate prefs file16:57
[reed]right now, all our apps have to duplicate the same prefs16:57
mconnorI said that, what, four minutes ago?16:58
mconnorwhy are you repeating my bitching? :P16:58
[reed]I didn't see where you said something like "all our apps have to duplicate the same prefs"16:58
mconnor[reed]: I said we need to do the toolkit prefs file17:07
mconnorand, no, we can just stick stuff in all.js17:07
mconnorthat's the current standard17:07
[reed]we do have non-toolkit apps17:07
[reed]they might not appreciate that17:08
mconnorwhy?17:09
mconnoryou think a few dozen prefs in all.js will impact those embeddors?17:09
[reed]I dunno17:10
[reed]maybe?17:10
mconnorit'd be cleaner, but meh17:10
[reed]I'll concede I'm making this up as I go.17:10
mconnordon't do that17:10
mconnorthere's been enough of that to date :P17:10
[reed]I blame you.17:11
[reed]anyway17:11
[reed]:)17:11
[reed]so, are you coming to UDS? :P17:11
mconnordon't think so17:11
[reed]sad17:12
mconnoreh17:12
mconnorwhere's the next one?17:12
[reed]no idea... will be announced on Friday of this one17:12
mconnorah17:12
mconnorI just don't want to travel any more this year17:12
mconnormy 40k miles of flying was my limit17:13
fta2you're not local ?17:13
[reed]hey, I've done 25k this year, not including this upcoming trip17:13
[reed]:)17:13
[reed]Thanks Mozilla and Canonical for footing my travel bills! :)17:14
[reed]fta2: he's Toronto-based17:14
fta2oh17:14
[reed]all the Mikes save one are Toronto-based17:14
[reed]I don't think we have any Mikes in MV now17:15
mconnormmm17:15
mconnorMikael Rogers?17:15
[reed]oh, true17:15
[reed]but he doesn't go by Mike, afaik17:15
[reed]could be wrong17:15
* fta2 is throwing thunderbird 3 and evolution through the window17:15
mconnor3?17:16
mconnorbold17:16
fta23 & 2, all the same17:16
[reed][10:45:33AM] <fta2> damn, i can't send emails using my corporate address using thunderbird (or evolution), while i can with mutt.17:16
[reed][10:46:54AM] <fta2> smtp+auth with tb and evo, NOK. evo with sendmail, NOK. mutt with sendmail, OK.17:16
fta2out17:16
[reed]France Telecom doesn't like open source.17:16
[reed];)17:16
mconnor[reed]: why'd you repaste that?17:16
mconnorI was just noting that trusting your mail to Tb3 is bold :)17:17
[reed]ah17:17
[reed]ok17:17
fta2i trust ff3.1 for the web17:17
mconnoryeah, but that's different17:17
mconnorif I nuke my mail, I can't do my job really17:18
fta2all the same to me. and i have logs, backups and even copies of my corporate emails.17:20
fta2i'm going back to mutt for now17:21
fta2now i remember why i've been using it exclusively since 199617:21
mconnorhehe17:22
[reed]I personally use Sylpheed, as I'm dependent on a GUI-based mail client for some reason... though, Sylpheed is about the only thing that can handle my mail17:22
[reed]Thunderbird fails miserably17:22
[reed]considering the amount of e-mail I get faily17:23
[reed]daily17:23
mconnorisn't your quantity of mail faily regardless of  your mail client? ;)17:27
fta299.5% of my incoming emails are spam. thanks to greylist/spamd/spamassassin/clamav, i'm just getting ~5% of spam at the end, 5% of 200~300 emails a day, 2/3 of mailing lists & bug tickets. procmail sorts those out, mutt can easily manage the rest.17:28
fta2asac, the new cairo is in. the next upload of xul will fail to build miserably17:30
fta2assuming 3.0 has the same problem as 3.117:31
=== stevel_ is now known as stevel
huayrahi18:59
huayraasac18:59
huayraas I was saying18:59
asachi huayra18:59
huayraI am interested in getting the swahili translation for ff3 going18:59
huayraI got resources and time for this18:59
huayraresources as in company backing18:59
huayraand I have a friend who is going to work with me on this19:00
asacoh cool19:00
huayramy question is if it is better to use rosetta or to go the l10n patrh?19:00
asacis there an official team for that language somewhere?19:00
huayrathere is one, but they have not done anything since 1.0.319:00
huayraat least nothing is been released19:00
huayraa mozilla team19:00
asachuayra: have you tried to talk to them?19:01
huayraI have contact with the lead, yes, but it seems to be lots of fractions in that team and nothing constructive coming out19:01
huayrahttps://bugzilla.mozilla.org/show_bug.cgi?id=30075419:01
ubottuMozilla bug 300754 in Registration & Management "[sw-TZ] Kiswahili Firefox localization (Kilinux Team)" [Normal,Assigned]19:01
asachuayra: if the team is somewhat active, it doesnt make much sense to use rosetta. unless the current team would be willing to do that19:02
asachuayra: how do they maintain their translations?19:02
mconnorhuayra: you should email l10n@mozilla.com and sethb@mozilla.com for help getting things unbusted, IMO19:02
huayrabasically no release has been done since 1.0.319:02
asacdo they have an (outdated) repository or something?19:02
huayrathat's ages ago19:02
huayrayeah, I have a link, let me find it19:03
asachuayra: do what mconnor said. once you know that you can take over the lead you can choose the tool you use to edit the stuff19:03
mconnorthere's a number of good translation tools for Mozilla19:03
asaci think a requirement is to have a complete translation19:03
mconnoryes, that is a requirement for being shipped as official, for obvious reasons19:04
huayrawhat should we use if we want the ubuntu community to contribute but also make upstream happy?19:04
asachuayra: rosetta as a tool would helpful if you want to tap the ubuntu translator community19:04
asacwhich sounds reasonable if the language is not a "major" one (excuse this word ;))19:04
mconnormmm19:05
mconnorI don't know why you'd translate for Ubuntu only19:05
asacmconnor: well19:05
huayrabut, if we want to make anyone happy and probably find a "framework" for such *minor* languages19:05
huayra?19:05
asacmconnor: we have lots of translators19:05
asacmconnor: they all use rosetta. so if you put things in there it gets automatically done ... e.g. you dont need to build your own community19:05
mconnorasac: that's not really an answer to "why translate only for Ubuntu"19:06
huayraI want to translate for everyone, not only Ubuntu, but rosetta (lp translations) has its adventages19:06
huayraso how can we get momentum and make everyone happy?19:06
mconnorhuayra: Axel and Seth can help here19:06
asacmconnor: most likely a matter of interest19:06
huayraI want a translated ff3 in all platforms and tap the ubuntu community for its momentum too in the effort19:06
asacmconnor: people just have to focus on something19:07
asaclike you focus on firefox19:07
mconnorthey're trying in the bug to resolve things, give them a shout, see what they can do19:07
huayrathey have been discussing since 2005. I want some real work done19:07
huayranot just talking19:07
* mconnor sighs19:07
huayraI am to use resources so I want results19:08
mconnoryes, because that localization team is being weird19:08
mconnorI'm not asking you to talk to to the existing team19:08
huayraif that means a one man show in rosetta so be it19:08
asacmconnor: the idea is to do translations in rosetta and find a way to get that shoved over to "official" tree19:08
huayrabut how can we fix things?19:08
mconnorI'm asking you to ask Seth and Axel for help19:08
huayrawe have contact with the team19:08
mconnorbecause that's their job19:08
asachuayra: yeah. talk to them ... about requirements and stuff19:08
huayraI am just asking you guys that know the real deal to find a solution19:08
huayraok19:09
mconnorhuayra: reading the bug, they've laid everything out19:09
huayraI will then talk to Seth and Axel19:09
mconnorthe existing "team" doesn't seem to be doing anything19:09
asachuayra: from rosetta point of view it would be interesting to get input on the exact formatting they require the translations to be done19:09
huayrayeah, I noticed that19:09
huayrathey just own the team, but no progress is been done19:09
mconnorso talk to them about restarting with a new team19:09
mconnorthey == who?19:09
mconnorSeth and Axel are the l10n drivers for Mozilla, they coordinate l10n across all locales19:10
huayraI was thinking of the team, not of S & A ;)19:10
huayraso in conclusion19:10
asacmconnor: they == Seth + Axel (and mozilla in general)19:10
asac(if you asked for my they ;))19:11
huayrais it possible to use rosetta and still get a usable translation for the upstream mozilla guys, or not?19:11
asachuayra: it is possible. if there are things that need to be fixed, we will certainly do that19:11
huayraisn't rosetta just handling the PO files anyway?19:11
asacits quite important for us to make things suitable for that19:11
asachuayra: firefox doesnt have po files19:12
mconnorheh19:12
huayraok19:12
huayraI reckon I will just talk to Axel and Seth and find out19:12
mconnorok19:12
huayrathank you very much guys19:13
asachuayra: its using xpi ... which is why its a bit more difficult. but rosetta has (beta) support for that. its just that we need more real-life19:13
asacto streamline stuff ;)19:13
huayraso this could be a nice opportunity?19:13
asachuayra: welcome19:13
asachuayra: for sure.19:13
huayraI mean to test the xpi support?19:13
asachuayra: right.19:14
mconnorer19:14
huayraok, interesting19:14
mconnorit uses XPI for langpacks, yeah19:14
mconnorbut that's the package format, not the output format19:14
asacmconnor: yeah. thats understood. its used as a synonym here.19:15
huayrayeah, xpi like in add-ons files19:15
mconnoras long as it outputs something that matches the in-tree format so we can get it upstream, great19:15
huayraso, what do we do?19:15
mconnorhuayra: that's your call19:15
mconnorhuayra: talk to the experts though :)19:15
huayrashall I try to get thing s working with the team and see if we vcan use rosetta, or just import the whole thing from mozilla when the translation in their terms is done?19:16
asachuayra: first sort out the admin stuff. then review the tools available on the market and decide19:16
huayrawhat are thos e tools?19:16
mconnorhuayra: Axel and Seth can give better recommendations19:16
huayracan you maybe point me to the tools that are used by other localization teams please19:17
huayraok19:17
huayrawhere do I find those guys?19:17
huayra#mozilla ?19:17
mconnorI'd email them19:18
mconnorand they're not likely on freenode19:18
mconnorsethb@mozilla.com and l10n@mozilla.com19:18
mconnorAxel's in Germany, Seth's in California19:18
huayrathnks so much :)19:19
asacomg ... my mailqueue was down again :(19:19
asacthats scary when you dont know which mails didnt go out for how long :(19:19
huayrado you guys know how many string FF3 has?19:32
asachuayra: i can look ;)19:33
mconnorasac: focus on looking at the big set of patches I have issues with, please :)19:33
mconnorhuayra: around 2k, at last check19:33
asac1893 messages + 3821 messages19:34
mconnor5k?19:34
mconnor6k?19:34
asacyeah19:34
mconnorhuh19:34
mconnormaybe19:34
mconnorI don't remember it being that high19:34
mconnorbut I don't translate :)19:35
mconnorasac: you saw my link?19:35
asacmconnor: yes.19:35
asacmconnor: i will start to push bugs tomorrow. 2h a day ... should be just a few days.19:36
asacmconnor: needs discussion should then be done in bugs19:36
asacmconnor: good enough?19:37
asacmconnor: [reed] already pointed out that 16 is required to move some classifier settings to toolkit19:37
mconnorasac: there's better ways to do that than adding another file to parse, fwiw19:40
huayraso 3800 strings?19:41
huayraor just 2k?19:41
huayrakind of fell off the conversation... ;)19:41
asachuayra: 3800 (toolkit) + 1600 (browser)19:42
asacer 180019:42
huayraasac excuse my ignorance. I want FF3 translated and all translators speak English. Do I need to strictly translate just 1600 or do I need the toolkit translated as well?19:43
asachuayra: toolkit is required19:44
huayraso 5400 strings is the translation requirement?19:44
asacyes about that amount19:44
huayrathx19:44
huayra:)19:44
asac560019:44
armin76lol19:46
mconnorasac: filing upstream bugs is the good first step, yeah19:47
mconnorasac: some of this stuff is, well, unnecessary19:47
mconnorasac: my biggest question was that in a couple of the patches you changed stuff inside of OSX #ifdefs, what was up there?19:49
asacmconnor: most likely i tried to make the patch complete ... if that completely doesnt make sense for OSX i was just wrong ;)19:50
mconnorasac: also, having a patch start with "supposedly this does X" is not ever something I want to see19:51
mconnorever19:51
mconnoreither it works or it doesn't :P19:51
asacmconnor: which patch is that?19:51
asacthe debian compatibility thing?19:51
mconnoryeah19:52
asacmconnor: i wanted to write "i hate debian for this" there ;) ... and ended up with a more political wording.19:54
asacmconnor: the patch obviously works ... otherwise it wouldnt be in there ;)19:54
mconnorwhy take it then?19:54
asacmconnor: background: we packaged xulrunner 1.9 and firefox 3.0 more than 6 month before debian did it.19:54
asacmconnor: then they started to make life miserable by doing some slightly different decisions19:55
mconnorasac: so, fun fact19:55
asacmconnor: problem is that when debian says we install stuff at place X ... then all the packages that we automatically sync would either not work19:56
asacor we would have to maintain a diff for them19:56
mconnorman19:56
mconnoryou guys should stop depending on Debian19:56
asacmconnor: and thats what debian guy did ;)19:56
mconnorwould make life so much easier19:56
asacmconnor: after he noticed that i work for canonical :)19:56
asacmconnor: previously debian xulrunner (1.8) had a patch system ... for 1.9 he eliminated that and now maintains stuff in a private git archive19:57
mconnorman19:57
asacmconnor: so when i want to understand what they did i have to look at the monolithic diff.gz19:57
mconnorI'm having flashbacks19:57
mconnorto the monolithic firefox-1.5 diff19:58
mconnor:P19:58
asacmconnor: firefox 3 is still monolithic. but thats eric as you might remember19:58
asacmike agreed for ages that we want individual patches19:58
asacuntil i started on ubuntu ;)19:58
mconnorman...19:58
mconnorthose guys19:58
mconnorso Mike has a private git repo, with a monolithic diff19:59
mconnorand Eric has a private SVN repo, or something, with a monolithic diff19:59
asacmconnor: yeah ;)19:59
asacmconnor: i think eric has a public git now19:59
asac;)19:59
mconnorquality software practices there19:59
mconnorlots of transparency19:59
* mconnor mumbles something about openssl under his breath20:00
asacmconnor: eric doesnt understand. mike does, but wants to pretend he doesnt understand :)20:00
asacmconnor: yeah. definitly a good example that we need to be much more skeptical about what debian does20:00
asacmconnor: of course its somehow unique. the majority of debian folks are quite good20:01
directhexpkg-mono are nice!20:01
asacproblem is that they are no team players20:01
asaceverybody focusses on his pet-package20:01
mconnorasac: yeah, I've noticed20:01
mconnorand they think they're experts20:01
asacand only cares about other things when it becomes a pain to locally workaround20:01
mconnorthat's my real worry with downstream20:02
mconnorespecially with mozilla, where we have too many dark corners20:02
mconnorits just not sane to assume that 1-2 maintainers will know the right way to implement something20:03
mconnor"Just because it works, doesn't mean its the right solution."20:03
mconnorand stuff where you're adding features that only work in Ubuntu is sadmaking20:04
wikifta: Hi21:09
ftawiki, hi21:16
wikithe patches in the debian/patches dir,how are they made ?using quilt ?21:16
ftaquilt new my_new_patch.patch21:19
ftaquilt add mozilla/some/file121:19
ftaquilt add mozilla/some/file221:19
ftaquilt diff21:19
ftaquilt refresh21:19
ftathat's the basics21:19
wiki:)21:20
wikifta: we released spicebird on 21st21:20
ftaexcellent21:21
ftaof course, you need to edit your files *after* the corresponding add and *before* the refresh21:23
wikifta: once i upload the files in lp via dput ,they get built themselves ?21:26
ftado you mean in a ppa ?21:26
wikiyeah21:26
ftathen yes21:27
wikifta: how long do these virtual monsters take ?40~45 minutes ?21:40
paranhi. I have for my personal use patched the flashplugin-nonfree package to download and install the new naitive 64bit plugin on amd64.21:47
parani will send my patch to bug 299146, but what do you think would be a good version number?21:48
ubottuLaunchpad bug 299146 in flashplugin-nonfree "flashplugin-nonfree on amd64 should use pure 64 bit plugin" [Wishlist,Confirmed] https://launchpad.net/bugs/29914621:48
paranright now I use 10.0.12.36ubuntu2~10.0.d20.7 (where 10.0.d20.7 is the amd64 version)21:48
asacwiki: they start to build quite instantly21:51
asacwiki: then the take the time they need and then it takes about 30 minutes until you can access the .debs21:52
wikiasac: cool21:52
asacparan: we will discuss during UDS how to properly package stuff up21:52
asacparan: we still want the nspluginwrapper option as we also use that for i386 to prevent crashes of core firefox21:52
wikiasac: we use ccache and disctcc on dual core debian etch with j8 flags to build our moz builds. It takes around 10 minutes :)21:53
asacwiki: if its more or less a full mozilla the builds usually take 25-30 minutes21:54
asacif you do more... add something on top ;)21:54
wikiasac: to make a deb for hardy,will it be called a backport ?21:55
paranasac: you mean use nspluginwrapper for all plugins on al arches then?21:56
wikiwhat if I mention as hardy in the changelog ,how will ppa interpret it ?21:56
asacparan: yes ... (optional for user)21:56
asacparan: so when amd64 is final we will not use nspluginwrapper for cross-arch ... only for out-of-process stuff21:57
asacparan: but what we want in the long run will be discussed during UDS21:57
asac(and how to achive that)21:57
asacparan: so atm if you install flashplugin-nonfree and have nspluginwrapper installed on i386 it will use nspluginwrapper21:57
paranasac: ok. if you do that then please make it on a per plugin basis. the current code always uses nspluginwrapper if it is installed21:58
asacif you dont have nspluginwrapper it will not use it21:58
asacparan: thats one of the points that is not yet clear21:58
paranasac: I will want naitive flash, but might need the wrapper for other 32bit only plugins21:58
asacparan: any ideas how the user is supposed to manage that?21:58
asacwe will discuss, but getting more ideas up-front will be helpful i guess21:59
paranyou could install both wrapped and unwrapped as alternatives22:00
paranso you could use update-alternative to select22:00
paranasac: I will put the nspluginwrapper code I ripped out back into my package. :) did you have any idea about the version name?22:03
asacparan: depends on where this will end up22:04
asacparan: update-alternative has to die imo :)22:04
asacparan: but the idea of having both installed is nice22:04
paranasac: hehe, why? I think alternatives is really useful, once you learn how to use it.22:08
paranasac: I just want to put some sort of sane version number before I send the patch in.22:09
paraneven if you decide to change how stuff work some of my (small) patch might be usefull, like downloading different tarballs dependin on arch22:11
asacparan: we dont need alternatives anymore. you can currently pick one out of many available plugins in ubufox ... this will hopefully later go into the main firefox UI22:13
asacparan: like: http://people.ubuntu.com/~asac/tmp/alt1.png22:13
asacparan: http://people.ubuntu.com/~asac/tmp/alt2.png22:13
asacparan: we would get two entries there for adobe: 1) adobe (native) 2) adobe (nspluginwrapped)22:14
paranasac: that would be nice.22:17
asacparan: yeah. i like it too. only problem we have to sort is that when you install nspluginwrapper post-mortem we would have to wrap already installed plugins too22:18
asacbut that can be done quite diligently i think22:18
asac(currently the wrapped stuff is only generated when you install flash after nspluginwrapper)22:19
paranyeah, I know :)22:19
paranhowever I would recommend keeping the alternatives link in addition to ubufox. there are other browsers that would need that22:19
asacparan: not sure. its really just clutter. konqueror does that on their own anyway22:20
asacepiphany is a use-case agreed22:20
asacbut then ... thats a missing feature in epiphany i guess and in the long run it will use nspluginwrapper22:20
asacerr22:21
asacit will use webkit ;)22:21
asacthats what i wanted to say22:21
asacbut well22:21
asacalternatives dont hurt for this mechanism22:21
asacits just that they regularly break on users system22:21
paranwould have been better if it were more integrated with dpkg, is is easy to mess it up with postinst/prerm scripts22:29
asacparan: maybe. but dpkg is from hell ... so fixing that there isnt easy either ;)22:32
parananyway, please don't remove the alternative for plugins unless you at least get the plugin chooser into the "normal" firefox package.22:32
asacparan: also even if you do it right, alternatives have strange behaviour22:32
asacfor instance if you --remove the last option it will remember that you selected nothing and when -install a new alternative it will not select the only one that exists then.22:32
paranI don't install ubufox because it pulls in a ton of gnome stuff22:32
asacparan: thats a different issue22:33
asacapturl needs to be fixed22:33
asacbut yeah22:33
asacbut as i said. this stuff is so cool that it belongs in the main firefox UI anyway22:33
paran:)22:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!