| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:sce-pkgcheck_command [2016/05/19 16:09] – nitram | dcore:sce-pkgcheck_command [2016/08/27 05:53] (current) – nitram |
|---|
| ===== dCore sce-pkgcheck Command ===== | ===== dCore sce-pkgcheck Command ===== |
| |
| The ''sce-pkgcheck'' command is not available in a default install and must be installed seperately from the dCore repository using ''sce-import sce-pkgcheck''. It is primarily used to ensure there are no non-existent packages in a list file (see ''sce-import -l LISTFILE'' help) when bulk installing a list of packages. This is useful to ensure the list file does not contain typographic errors, the package exists, whether it comes from the main, security, extra, or prebuilt repositories or is part of a meta package in the dCore dependency list file on the server. | The ''sce-pkgcheck'' command is useful to confirm packages and repository of origin (ie. main, security, extra, dCore prebuilt, metapackage). It is also useful to check packages imported via list files. Run [[http://wiki.tinycorelinux.net/dcore:sce-import_command|''sce-import --help'']] and review ''sce-import -l LISTFILE'' for more information. |
| |
| Be aware the dependency list files used on the server to add needed dependencies also have entries that may not exist in the dCore variant being run. For example, if a package in Debian Wheezy based dCore needs libgcc-4.7 and an Ubuntu Trusty based dCore needs libgcc-4.8 then both are added to the dep list. This same logic is used when processing the list (*.lst) files. | As ''sce-pkgcheck'' is not included in a base dCore install, it must be imported separately from the dCore repository, to use: |
| | sce-import -o sce-pkgcheck |
| | sce-load sce-pkgcheck |
| | sce-pkgcheck PKG |
| | |
| | Note dependency list files from the dCore server contain dependencies that may not exist in the particular dCore variant being run. For example, if a package in dCore-wheezy needs libgcc-4.7 and dCore-trusty needs libgcc-4.8, then both are present in the dCore server's dependency list. This same logic is used when processing the list (*.lst) files. |
| |
| Usage options from the 'sce-pkgcheck --help' command: | Usage options from the 'sce-pkgcheck --help' command: |
| |
| sce-pkgcheck leafpad will update the DEBINX files, check if leafpad is a package and display the repo. | sce-pkgcheck - Check individual PKG (package) to confirm name and repository of |
| sce-pkgcheck -p leafpad will not update DEBINX, check if leafpad is a package and display the repo. | origin, including PKGs not currently installed. Can also check |
| sce-pkgcheck -q leafpad will not update DEBINX, check if leafpad is a package and display the repo. | PKGs from SCE list file(s) located in /etc/sysconfig/tcedir/sce/ |
| sce-pkgcheck -l leafpad will check the specified file list. | (eg. typo in list file). Results echoed to /tmp/.pkgcheck. |
| sce-pkgcheck -a will check all your .lst files in your SCE directory. | May use option combinations (eg. sce-pkgcheck -paq). |
| | Run 'sce-import --help' regarding list files. |
| | |
| | Usage: |
| | |
| | sce-pkgcheck PKG Update DEBINX, confirm the PKG and repository. |
| | sce-pkgcheck -p PKG Preserve DEBINX, confirm the PKG and repository. |
| | sce-pkgcheck -q PKG Quiet mode, update DEBINX, terminal output only if PKG |
| | not available, full output echoed to /tmp/.pkgcheck. |
| | sce-pkgcheck -l SCE.lst Check PKGs in specific SCE directory list file. |
| | sce-pkgcheck -a Check PKGs in all SCE directory list files. |
| |
| **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** | **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** |
| |
