Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
 Share

4,261 posts in this topic

Recommended Posts

Looks like the line endings don't make difference, but on your next commit, update the file with this one

http://www.insanelymac.com/forum/index.php...t&id=100319

 

The one in trunk 1411 has some translation errors.

 

You right!

 

I do some local test and the pkg support the pt and pt_PT

 

I commit the changes.

 

:)

Fabio

Link to comment
Share on other sites

Nice, but the brazilian version still has the translation errors in trunk ("provides" translates as "fornece" and not "provê" as I wrote in the earlier version).

 

This one is correct

http://www.insanelymac.com/forum/index.php...t&id=100319

 

EDIT: no, I'm wrong, the file is correct, just the pkg has the wrong translation, should be fixed in next build.

Link to comment
Share on other sites

Nice, but the brazilian version still has the translation errors in trunk ("provides" translates as "fornece" and not "provê" as I wrote in the earlier version).

 

This one is correct

http://www.insanelymac.com/forum/index.php...t&id=100319

 

EDIT: no, I'm wrong, the file is correct, just the pkg has the wrong translation, should be fixed in next build.

 

I'm bit confused...

 

example of your posted file:

"uClibc_title" = "uClibc++";
"uClibc_description" = "Este módulo [color="#FF0000"]fornece[/color] uma biblioteca runtime C++ minimalista para uso em outros módulos.
Ele não [color="#FF0000"]fornece[/color] funcionalidade por si só, mas é usado para permitir o uso da linguagem C++ em outros módulos.
Observe que rtti e exceptions foram ambos desativados.
Fonte: [url="http://cxx.uclibc.org/"]http://cxx.uclibc.org/[/url]
Dependências: klibc";

 

so is ok fornece for brazilian pt_PT ????

(this field coming from your file)

 

Fabio

Link to comment
Share on other sites

so is ok fornece for brazilian pt_PT ????

(this field coming from your file)

Yes, it's ok for both pt and pt_PT.

 

But I tested Chameleon-2.1svn-r1420.pkg and it shows pt_PT translation even my system being set up as brazilian portuguese.

Link to comment
Share on other sites

Again how can i use that builds?

I always get that error and if i show package content i see lots of sub .pkg but where is the main to get started as the RC 2 build before?

 

No idea mitch_de...

You try to compile the pkg by yourself?

 

Yes, it's ok for both pt and pt_PT.

 

But I tested Chameleon-2.1svn-r1420.pkg and it shows pt_PT translation even my system being set up as brazilian portuguese.

 

I do the change later.

 

Fabio

Link to comment
Share on other sites

"No idea mitch_de...

You try to compile the pkg by yourself?"

No, i dl the Xcode 4.1 ,pkg and want to use it as installer.

Must i do something (make an installer )with that download first before i can use it (by doubleckick)?

Link to comment
Share on other sites

"No idea mitch_de...

You try to compile the pkg by yourself?"

No, i dl the Xcode 4.1 ,pkg and want to use it as installer.

Must i do something (make an installer )with that download first before i can use it (by doubleckick)?

Mitch, i still didn't understood your problem??! :(

Download the pkg e.g. Chameleon-2.1svn-r1427.pkg.gz, unpack it and run it...

Well, i really don't recommend running it, not just yet... needs some fixing; i'm taking a look at it.

Link to comment
Share on other sites

Well, i really don't recommend running it, not just yet... needs some fixing; i'm taking a look at it.

I tried running the official package installer the other day when Chameleon 2.0 was released but I found it failed when choosing the GraphicsEnabler boot option. I posted an issue at the forge about it. I haven't tried again since.

Link to comment
Share on other sites

I tried running the official package installer the other day when Chameleon 2.0 was released but I found it failed when choosing the GraphicsEnabler boot option. I posted an issue at the forge about it. I haven't tried again since.

Well, for now i'm just looking at the install scripts. I will post progress on the Voodoo forums topic.

Link to comment
Share on other sites

Mitch, i still didn't understood your problem??! :P

Download the pkg e.g. Chameleon-2.1svn-r1427.pkg.gz, unpack it and run it...

Well, i really don't recommend running it, not just yet... needs some fixing; i'm taking a look at it.

 

I always gettings this (with 10.7.2 C37, no other probe with my system)

"18.08.11 19:28:14,849 Installer: The package "Chameleon-2.1svn-r1427" could not be opened. This can happen if the package has incorrect permissions or if the package has been renamed.

18.08.11 19:28:14,849 Installer: PFPackage::packageWithURL - can't instantiate package: /Users/andreas/Desktop/Chameleon-2.1svn-r1427.pkg

18.08.11 19:28:14,849 Installer: Invalid Distribution File/Package"

 

I copied to desktop, also same problem to any other place. I have no permission problems with desktop

Bildschirmfoto_2011_08_18_um_19.26.44.jpg

Link to comment
Share on other sites

I always gettings this (with 10.7.2 C37, no other probe with my system)

...

I just tried both XCode 4.1 & 4.0.1 r1434 and they run as usual.

Can you compile with XCode 3?

If not, here's one built with 3.2.6 on Snow: Chameleon_2.1svn_r1434.pkg.gz

Remember what i said on the other post ;)

Link to comment
Share on other sites

Thanks, your builds 3.2.6 on Snow: Chameleon_2.1svn_r1434.pkg.gz worked (means installer starts up without error).

I am a bit ??? why all other builds (LION Xcode 4.x) gave that error even i have LION 10.7.2 running.

Also what i don't understand is, that yours seem to be normal .pkg (can't use show finder content) , the others are different, they all can be used by show finder content and have much sub.pkg inside.

Link to comment
Share on other sites

Thanks, your builds 3.2.6 on Snow: Chameleon_2.1svn_r1434.pkg.gz worked (means installer starts up without error).

I am a bit ??? why all other builds (LION Xcode 4.x) gave that error even i have LION 10.7.2 running.

Also what i don't understand is, that yours seem to be normal .pkg (can't use show finder content) , the others are different, they all can be used by show finder content and have much sub.pkg inside.

Mitch, most probably Lion doesn't like the way the pkg is built and the buildpkg.sh needs to be updated..?!

I can't test this on Lion because i don't run it. Will talk to the guys about it; we need the buildbot running a XCode 3 build.

Do you know of anyone else having the same problem?

 

these are inverted, pt is brazilian portuguese and pt_PT is portuguese (from Portugal).

yeah... and Brazilian Portuguese should be pt_BR ;)

Link to comment
Share on other sites

Mitch, most probably Lion doesn't like the way the pkg is built and the buildpkg.sh needs to be updated..?!

I can't test this on Lion because i don't run it. Will talk to the guys about it; we need the buildbot running a XCode 3 build.

Do you know of anyone else having the same problem?

 

 

yeah... and Brazilian Portuguese should be pt_BR ;)

 

 

omg...

 

So? oldnapalm can you test and report the working way?

 

Brazilian(portuguese) pt_BR or pt_PT

Portuguese pt or pt_PT

 

Fabio

Link to comment
Share on other sites

pt = Brazil

pt_PT = Portugal

Oldnapalm, i think you need to read some about country and language codes.

Since when pt = Brazil??

And iFabio, this stuff was fine as it was, imho.

 

Anyway, i don't really care...

Link to comment
Share on other sites

Oldnapalm, i think you need to read some about country and language codes.

Since when pt = Brazil??

And iFabio, this stuff was fine as it was, imho.

 

Anyway, i don't really care...

I don't care too, but that's how it is in default Lion apps, pt.lproj for brazilian and pt_PT.lproj for portuguese. Maybe it's different in this installer, I don't know. I can tell it's working fine in r1440.

 

Edit: I found this

For some languages, there are regional variations (e.g. Standard vs. Brazillian Portuguese). Apple recommends that you use "pt.lproj" for non-region-specific Portuguese, and "pt_PT.lproj" and "pt_BR.lproj" for region-specific localizations. Whenever you include a region-specific locale, though, you should also include the non-region-specific locale (for example, if you include either "pt_PT.lproj" or "pt_BR.lproj", you should include "pt.lproj"). If a resource has a value common to both, for example "pt_PT.lproj" and "pt_BR.lproj", then you can put it in "pt.lproj", and both "pt_PT.lproj" and "pt_BR.lproj" users will pick it up from there. You can omit resources from the region-specific .lprojs, but not from the non-region-specific ones.

 

For what I understand, brazilian uses standard pt.lproj

 

from /Applications/Mail.app/Contents/Resources/pt.lproj/Localizable.strings

"caixas de correio selecionadas"

 

from /Applications/Mail.app/Contents/Resources/pt_PT.lproj/Localizable.strings

"caixas de correio seleccionadas"

 

but differences are so small that I wouldn't bother having 2 translations.

Link to comment
Share on other sites

 Share

×
×
  • Create New...