xarchiver - inaccessible command line archivers tools

[AbNoRMiS]

xarchiver.scm were converted with
the following archivers extensions

Code: [Select]

arj.tcz
bzip2.tcz (somehow not entirely)
cpio.tcz
gzip.tcz
p7zip-full.tcz
tar.tcz
unrar.tcz
xz.tcz
zip-unzip.tczbut since in tinycorelinux adopted prefix is /usr/local
through this difficult to use these archivers from command line
because binaries /apps/scm_name/local/bin/* are nowhere linked
nor to /apps/bin nor to /apps/local/bin which would be in the path
because such local dir as /apps/local/bin generally not provided

perhaps these problem are present also in other self-contained modules
how dispense in this case without installing duplicative extensions or modules?

[Jason W]

Binaries that are buried in an scm are there only to support the main app, in this case xarchiver.  They are not intended to be available for general use by the command line.  What is meant to be available for general use of the scm is found in /apps/extname/bin, in which they get linked to /apps/bin. 

By definition there is going to be duplication of internal files with the scm approach, though there should not be duplication among what is in /apps/extname/bin between extensions as that would cause file conflict when both scms are installed.

[AbNoRMiS]

that is if i understand correctly
if the self-contained module compiled rather than converted from extensions
then configuring of apps with deps should have --prefix=/apps/scm_name/local
but not --prefix=/apps/scm_name as this specified in SCM Basics
in order to eliminate file conflicts?

[AbNoRMiS]

or considering the above follows that there is no sense specially compile self-contained modules?
can assume that self-contained module building algorithm reduces to compile apps with its deps
and then using existing script to convert obtained regular extensions to self-contained module?

[Jason W]

Now I am using -

./configure --prefix="$PKGPATH"  --bindir="$PKGPATH"/localbin

as the general compile options, PKGPATH would be /app/xarchiver if I were building from source.

Sure, many of those binaries in /apps/extname/localbin, or /apps/extname/local/bin could be removed to save space if they are not needed.  I imagine xarchiver would need those archiving binaries contained in it.  I tried to remove some binaries out of filezilla to save space, but the extension was then broken, though I am sure some could be removed.

Using --prefix=-/apps/extname/local would also prevent conflict, but I would have to redo the buildscm script to accomodate it, which I may try to do so it is an option.  There are ongoing improvements made to the scm format that are not yet reflected in what is available in the repo.  In time, it will become more standardized.

[AbNoRMiS]

then i have a question about xampp-linux.scm

whether means all the above that is necessary prevent linking of all binaries
from /apps/xampp-linux/bin/* to /apps/bin except main script lampp?
(which i did intentionally thinking that they can be used from the command line)

[Jason W]

Ideally I would think that it is best to not have support binaries in /apps/extname/bin, but at this point it is not a hard and fast rule, but if file conflicts arise that cause issues between scms, then we can deal with them as they arise.