This is much more complicated than at first glance. Updated draft sce-import --help below. Please review Jason W and/or jls_legalize, any more devils in the details? Also, does the *.sce.lst file need to be placed in /tce/sce before running import? Trying to stay away from specific package names, but sce-import is quite a bit more complex.
sce-import - search, convert, install DEB and pre-built packages as local SCEs,
use simple DEB and pre-built package names, example 'emelfm' not
'emelfm.tar.gz', 'nano' not 'nano_2.2.6-3_i386.deb', may use
some option combinations, example 'sce-import -zbrs nano'.
Usage:
'sce-import' prompts for starting characters of package sought.
'sce-import PKG' search packages that start with desired package name.
'sce-import -c PKG' search packages that contain desired package name.
'sce-import -l FILENAME' create an SCE mega-extension from an *.sce.lst file,
a plain text file that lists one package per line,
may include both DEB and pre-built packages.
'sce-import -b' add resulting SCE extension to sceboot.lst.
'sce-import -r' use RAM for unpacking source DEBs.
'sce-import -s' list sizes of packages to be fetched and installed.
'sce-import -d' use existing SCE extensions as dependencies.
'sce-import -o' add resulting SCE extension to ondemand.
'sce-import -n' non-interactive mode.
'sce-import -u' (DEFAULT) update mode, sync new debinx files.
'sce-import -p' use existing debinx, no new fetch, better performance.
'sce-import -v' see list of packages the imported SCE contains.
'sce-import -z' use only CLI options, ignore etc/sysconfig/sceconfig.
PS - Don't mean to sidetrack krooooo, figured these details would be helpful to your original post.