dCore Import Debian Packages to Mountable SCE extensions > Allwinner A10

Import Debian Wheezy Armhf Packages

<< < (5/11) > >>

roberts:
With the latest discussion of dwb gui web browser imported and running great on the Allwinner Arm platform, just for kicks...
Using my latest import suite of scripts, I imported dwb on Raspberry Pi. I am posting this via dwb on Raspberry PI.  8)
Only one small adjustment which can easily be added to startup script, and later will be automatic via importscripts on server.
That being compiling desktop schemas. It is not as fast as Allwinner, which is to be expected but useable.

roberts:
I just uploaded import v0.4 suite of utilites.
New utilities are mkcpio, loadgz, and updstartscript

Use mkcpio to turn a package import directory into a single cpio gz.
You may then place the .gz in the root of your tce directory for much improved load times.
A good use of this new option is xorg. Using xorg.gz allows boot to X desktop in approx 15-20 seconds. I also use it for dbus. Note these load to ram so careful what you choose. Always have swap.

loadgz is similiar to load-tce. Make a gzs directory under your tce directory. Then load additional cpio gzs with loadgz. Startup scripts are honored.

Finally updtstartscript, will allow quick and easy access to create or update a tcz's startupscript. It unpacks, calls vi to edit the extension's startup script, and then repacks the extension.

sbp:

--- Quote from: roberts on December 11, 2012, 10:23:28 PM ---Using my latest import suite of scripts, I imported dwb on Raspberry Pi. I am posting this via dwb on Raspberry PI.  8)
--- End quote ---

Hi Roberts

I now have a working version of tinycore on the raspberry (4.7.2), and would like to try to import some of the Debian packages, however, I cant find the import.tcz in the Raspberry part of Army Core.
So do I simply take it from the Allwinner repro and use it in raspberry or?

 

roberts:
Import from Allwinner supports Raspberry Pi.

Note however that my focus is first towards Allwinner as I do little import testing on Pi.
I now use my Pi as a local server and only boot a desktop to test new Core images as I build them.

I am currently revisiting Core's base to make it more resilient with regards to the use of imported packages.

While I, as well as several others, have a complete desktop, with GUI browser, all via import. Import is still at a very early stage of development with many changes forthcoming.

After I finish hardening Core I will revisit import for better support of more packages and a smoother operation.

The goal remains the same. Import is to be an additional option across all platforms, just as community built tczs and community built scms. Import's goal is to offer a wide range of available packages while maintaining Core unique feature of pristine boot and ultra fine grain control of applications to be loaded. 

Initial milestones will continue to target Allwinner. Others to follow.

sbp:
Thank you for the answer.
But how do i use it in raspberry, i mean i cant install the import.tcz on my raspberry, as it is not available for the raspberry?

Navigation

[0] Message Index

[#] Next page

[*] Previous page