You are here: welcome » dcore » ppa-deb2sce_command

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
dcore:ppa-deb2sce_command [2016/06/07 03:23] – created nitramdcore:ppa-deb2sce_command [2016/08/27 05:21] (current) – nitram
Line 1: Line 1:
 ===== dCore sce-deb2sce Command ===== ===== dCore sce-deb2sce Command =====
 +Occasionally a user may wish to import a single package (*.deb file) from outside the standard Debian or Ubuntu repositories. This can be accomplished with the ''sce-deb2sce'' command, a small script not part of a base dCore install. To obtain and use ''sce-deb2sce'' download the desired *.deb file and run:
 +    sce-import -o sce-deb2sce
 +    sce-load sce-deb2sce
 +    sce-deb2sce <DEB-file>
  
-Occasionally a user may wish to import a single package ('*.deb' file) from outside the standard Debian or Ubuntu repository. This can be accomplished with the ''sce-deb2sce'' command. It's a small script not part of a standard dCore installation. To obtain, simply download it from the dCore repository and load it for use: 
-<code> 
-sce-import -o sce-deb2sce 
-sce-load sce-deb2sce 
-</code> 
  
-Usage: +The new SCE can then be loaded for use, run: 
-<code> +    sce-load /path/to/file/my_new.sce
-sce-deb2sce <DEB-file> +
-</code>+
  
-Similar to running ''sce-import'', an SCE is created in the current working directory.+Alternatively move 'my_new.sce' and 'my_new.sce.md5.txt' to /etc/sysconfig/tcedir/sce/ so it is recognized by the system. Then either add the newly created SCE to sceboot.lst, OnDemand or manually load using ''sce-load''. To add the SCE to OnDemand, review the [[dCore:sce-ondemand_command|dCore sce-ondemand Command]].
  
-Since all SCEs now require a proper md5sum file to load, this should be created: +Note *.deb file names usually contain the version number, which may be helpful to keep, even though a more generic extension name may be desired. This can be achieved, for example, by moving the newly created version number SCE file (eg. my_new_2.5.3-3_i386.sce) to /tce/import/debs/ with a generic name symbolic link in /tce/sce (eg. my_new.sce).
-<code> +
-md5sum my_new.sce > my_new.sce.md5.txt +
-</code>+
  
-* Please consider submitting a patch to auto-generate the md5sum file :)+Usage options from the 'sce-deb2sce --help' command: 
 +  sce-deb2sce - Convert a single Debian package (*.deb file) into an SCE. 
 +                Useful to import a *.deb file not present in dCore's existing 
 +                Debian or Ubuntu repositories. Resulting *.sce and *.sce.md5.txt 
 +                files can be moved into /etc/sysconfig/tcedir/sce/ to be 
 +                recognized by the system. 
 +   
 +                The SCE and any dependency SCE(s) required to run the software 
 +                must be loaded with sceboot.lst, sce-ondemand or sce-load. If 
 +                numerous dependencies are required, importing them as a 
 +                list file may be easiest, see sce-import --help. 
 +   
 +  Usage: 
 +   
 +  sce-deb2sce debian_package.deb   Convert specified *.deb file into an SCE.
  
-The new SCE can then be loaded for use by running: +**[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
-<code> +
-sce-load /path/to/file/my_new.sce +
-</code> +
- +
-Although it's likely best to move 'my_new.sce' and 'my_new.sce.md5.txt' to /tce/sce/ so it will be recognized when running ''sce-load''. +
-<code> +
-sce-load  # Load my_new.sce from menu +
-sce-load my_new.sce  # Direct loading +
-</code> +
- +
-Note '*.deb' file names usually contain the version number, which may be helpful to keep, even though a more generic extension name may be desired. This can be achieved, for example, by moving the newly created version number SCE file (eg. my_new_2.5.3-3_i386.sce) to /tce/import/debs/ with a generic name symbolic link in /tce/sce (eg. my_new.sce).+
  
Print/export
QR Code
QR Code dcore:ppa-deb2sce_command (generated for current page)