WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Extensions for testing  (Read 7609 times)

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Extensions for testing
« Reply #15 on: December 10, 2012, 06:11:17 PM »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Extensions for testing
« Reply #16 on: December 10, 2012, 06:19:00 PM »

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 10812
Re: Extensions for testing
« Reply #17 on: December 10, 2012, 06:35:43 PM »
Hi Jason W
Are these to replace the ones listed in replies #3 and #8? Should I update the index to point to these two instead?

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Extensions for testing
« Reply #18 on: December 10, 2012, 07:39:25 PM »
Yeah, these are the same files, an 'update' as they are now available. 

Online Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 10812
Re: Extensions for testing
« Reply #19 on: December 10, 2012, 07:52:58 PM »
Hi Jason W
OK, index updated.

aus9

  • Guest
Re: Extensions for testing
« Reply #20 on: December 11, 2012, 03:26:06 PM »
I have decided until I get feedback to have 2 package names
sox
-------meaning sox without pulseaudio support, the same as current version and
sox-pulse
---------------for those who need pulseaudio support.

for both versions I found this guide useful
http://www.thegeekstuff.com/2009/05/sound-exchange-sox-15-examples-to-manipulate-audio-files/

Both are versions 14.4.0
The docs for sox is relevant for sox-pulse and both have a dev package

1) sox download  bcrypt password is tinycore
current maintainer has given permission for me to test new packages.
https://sites.google.com/site/gordontinycore/sox

2) New sox-pulse, password is tinycore
https://sites.google.com/site/gordontinycore/sox-pulse

good luck
« Last Edit: December 12, 2012, 01:59:32 AM by aus9 »

aus9

  • Guest
Re: Extensions for testing
« Reply #21 on: December 16, 2012, 05:14:10 AM »
I know this page will be destroyed shortly

I have completed a tcz with an EULA that must be agreed to by the user, if they want a Google supplied pepper flash plugin that works with the chromium-browser

As this may be a little controversial I am prepared NOT to submit it, if I get too much flak or flak from important people

Normally I would have the bfe there but its bigger than 20 Megs due to it having the source deb file.
The source file can be grabbed by running the getpepper script but be warned this downloads a huge file which is Google Chrome.

https://sites.google.com/site/gordontinycore/pepper
« Last Edit: December 17, 2012, 03:41:18 PM by aus9 »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Extensions for testing
« Reply #22 on: December 19, 2012, 11:54:23 AM »
hi coreplayer2,

icecat-17.0.1 works flawless for me,
although i didnĀ“t load any other mozilla-package before,
no firefox, no minefield, no seamonkey,
even no thunderbird...
this link to /usr/local/bin wasn't needed yet, at least for me.

keep on digging!

Well today I installed Firefox 17 on a clean tinycore64 system and have the exact same issue as before

Code: [Select]
XPCOMGlueLoad error for file /usr/local/firefox-official/libxpcom.so:
libxul.so: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

The file exists in (as before with icecat) "/usr/local/firefox-official/"

Am attempting to symlink this directory to get firefox to load,  so far have no functioning browser, all deps are loaded.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10862
Re: Extensions for testing
« Reply #23 on: December 19, 2012, 11:56:44 AM »
Closing this topic, as we're back up.
The only barriers that can stop you are the ones you create yourself.