:: Chromium on Slackware - Part 4 ::

A very quick post to inform that I finally created a repository for this project on github: github.com/yucatan/chromium

Now all the updates will be done there. Enough of waiting on rapidshare for you guys ;)

:: Chromium on Slackware - Part 3 ::

OOOOK, more news on the subject. I finally built chromium packages from those smaller sources, so a new slackbuild was born and new packages of chromium are ready. Plus, a new dependency (yasm) showed up, but that's no big deal. On Slackware64-13.1 and current we already have the package for yasm. If you are running Slackware-13.1 (32bit) you will need to build the package yourself (get the the slackbuild here.

Bellow are the links to download the slackbuild and the packages:

• chromium.SlackBuild
• chromium-7.0.542.0-i486-1_ken.tgz
• chromium-7.0.544.0-x86_64-1_ken.tgz

Edit: I just edited the links above!

OK, have fun and don't forget to tell me if you have any problem with them.

:: Chromium on Slackware - Part 2 ::

A very quick post just to share the news. Today I came up with the SlackBuild script for Chromium, plus two new packages, one for x86 and one for x86_64. Ah, and I changed the repository from mediafire to rapidshare.

To download go here (the links are now dead, please the post "Part 3"). It should open a "folder" containing the three files. Download whatever suits you best.

Feedback is welcome, of course.

:: Chromium on Slackware ::

OK, unlike other Chrome/Chromium packages for Slackware we see "floating" around the internet, this time we DO have a Chromium package which is REALLY made for slackware. What's the problem with the other packages? Well they were made like one of these options:

1. people pick up DEB (or RPM) packages, unpack them, then repack as TGZ or TXZ
2. people pick up the builds google release, then make packages (TGZ or TXZ) for slackware.

OK, you still don't have a clue for what is the problem, right? Simple to show. Please open your Chrome/Chromium on slackware, then go to any site you can upload files. Now choose to upload a JPEG/JPG file. Yes, your browser crashed as soon as you clicked on that JPG file, right?

"WHAT THE HELL HAS JUST HAPPENED?" You might be asking yourself (or me). I posted a bug repport about that (like many other users, even of many other distros, did). So the good people on google (chrome/chromium team) said the problem is related to libjpeg. They use one version of libjpeg when building their packages (for Debian/Ubuntu or RedHat). Then on Slackware we have a different version of libjpeg. When Chrome tries to create/show the preview for that JPG file you clicked (to try and upload) some sort of "conflict" shows up and the browser goes to hell. They (google) advise to compile chrome from source, which should remove the problem.

So yesterday I finally took time to download all that HUGE source code (more than 800MB) of chromium. Decompressed it, synced with their SVN... and then I compiled Chromium ON SLACKWARE, FOR SLACKWARE.

That said, now we have packages (chromium and deps) for Slackware64-13.1 on the links bellow:

chromium-7.0.541.0-x86_64-1_ken.txz

GConf-2.28.1-x86_64-1_SBo.txz

gnome-keyring-2.28.2-x86_64-1_SBo.tgz

libtasn1-2.8-x86_64-1_SBo.tgz

ORBit2-2.14.17-x86_64-1_SBo.txz

(the above links are all dead now. Please see the post "Part 3")

As soon as I get a VM running slackware-13.1 (32bits) I will get packages for that architecture too.

OK, let me know if you have any problems using these packages, chromium, etc.

Lunch time.

:: DVD Player ::

:: DVD Players ::

Vejam só. A gente vai e compra um aparelho de DVD (DVD Player) que também toca/roda videos em DiVX, certo? É a 11ª (ônzima) maravilha do mundo. Eeeeba! Mas daí um dia descobre que não é tudo isso.

What the fuck?

Não sei o DVD player de vocês, mas lá em casa nós temos dois: um da Philips e um portátil da Normende que commpramos no Uruguai de presente pra minha filha. O bom desse portátil é que ele tem entrada USB, então dá pra espetar um pendrive ali e rodar os vídeos, sem precisar gastar DVDs pra isso. Porém esses nossos aparelhos têm uma limitação. Não rodam filmes em alta definição (HD). Ou seja, se tentar rodar um video que esteja em 720x480... pode esquecer, eles não aguentam. Ou eles simplesmente não conseguem carregar o filme, ou levam um tempão pra carregar, só que daí "só sai o audio". Legal né :(

A explicação deve ser simples: o processador que tem dentro desses aparelhos, que faz a descompressão/decodificação dos videos em DiVx não tem potência suficiente para fazer o serviço quando os videos estão em HD. E a gente acha que rolaria, visto que os filmes em um DVD-Video (DVD normal) estão em HD né. Só que os DVD-Video usam videos em MPEG2, não em DivX.

Então, crianças, aí está a explicação para o "problema". Na próxima compra de um dvd player que rode divx (se é que já não se vai pular direto pra um blueray player) prestem atenção nisso e vejam se conseguem testar rodar algum video DivX em HD ;)