dCore Import Debian Packages to Mountable SCE extensions > dCore X86

Debian Jessie dCore

<< < (12/19) > >>

netnomad:
hi jason,

sorry for my misleading, imprecise message!

i mean the md5sum-file for the last cut of dCore-jessie.gz

http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz.md5.txt
bd3a30f6a2f43e90433da65b2c475445  dCore-jessie.gz

then the md5sum of the just downloaded file from that url:
tc@box:~/tmp$ md5sum dCore-jessie.gz
dde5dc98bd3977099ca8310d38bd64d9  dCore-jessie.gz

Jason W:
Oops, I had left the md5sum file in place from the unpack of the previous cut as a filename marker and forgot to remake it.  Should be good now.

Jason W:
Updated to change the "importsce -f" option to the more logically named "importsce -l".  Also, a /etc/sysconfig/tcedir/sce/pkgname.sce.lst file is created out of that specified file list.  That .lst list will be used on future import sessions of that package name whether a Debian one or one of the user's choosing.  Using the "importsce -l" option on future imports of that package name with an expanded package list will create a new sce with those packages and also overwrite the previous .lst list file.   

http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz

http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz.md5.txt

Jason W:
Fkxed a warning message that occurs when the list file option is not used, uploaded new cut.

netnomad:
hi jason,

i didn't understand the concept of the *.lst-files yet.

so
1. i need a file with the packagelist, that's named f.e. mypackage
2. the command "importsce -l mypackage" copies the file to mypackage.lst
3. mypackage.lst is used for the import-process

i guess that usually mypackage and mypackage.lst are identical, what's the idea behind that?
mypackage is needed for the command, mypackage.lst is needed for the import-process?

thank you for your support and help.

Navigation

[0] Message Index

[#] Next page

[*] Previous page