few service questions

[dicorer]

well, thanks for the "Yes, you are right" ... most of the people I work with, in the best case they would turn around and say "sorry Im busy now"

[Jason W]

Thanks JLS and Onyarian for your help.

dicorer - as has been said, forum searches would reveal much of this stuff.  And my advice would be to then use dCore in the standard recommended manner, or expect breakage. 

As for opera, there is a repo for it, I just imported it:

http://forum.tinycorelinux.net/index.php/topic,17807.0.html

[dicorer]

I might wrong, but most of the questions Im asking, are not available by forum search, and I see even the senior members dont have very clear control of the tool.
But thats not a problem.
Latest issue, it seems me and Onyarian just used dCore in the standard & recommended manner, nevertheless it broke.
But also thats not a problem of course.

Instead, I simply would like to kindly ask you, if you could please answer my previous questions, which got lost:

you mean to use a Debian Packages file on ub-dCore-trusty or ub-dCore-utopic?

I guess, I mean yes, setup sce-import to load the default index DEBIAN file containing all packs dependencies, and dl a DEBIAN pack... is that possible (implemented feature)?

I would not recommend it

Why not?
Smtng nasty with DEBIAN architecture? or what is it?

Thanks

[Jason W]

Debian Wheezy packages are made to work with Wheezy, in terms of library versions and other compatibility.  Same with each Debian and Ubuntu release.

Using packages from Jessie on Wheezy are going to cause problems if they even work at all.  Nothing wrong with the Debian package pool, just needs to stay with the right release.  If you want Debian Jessie packages, simply use dCore-jessie.  You can change the values in /usr/share/doc/tc, but do so at your own risk as things will break.

I imported Opera, and the import session and package worked. Should not matter if it is dCore or ub-dCore, Opera is binary and works with all.


Below works for me:

Create file /opt/debextra/opera

Put the below entry in that file:

http://deb.opera.com/opera/ stable non-free

sce-import -n opera

It imports, and loads, and works.

I wish I could reproduce the errors.  I will reboot with ub-dCore-utopic to make sure opera works.

[Jason W]

Ok, I see the bug in the ub-dCore-utopic import of opera.  It has nothing to do with Debian versus Ubuntu, but a script bug.  I will check into it.

[Jason W]

Simple fix, uploaded.  See Release thread for details.

[dicorer]

any reason why exists ub-dCore-utopic.gz/bin/lsmmod ?

[Jason W]

Busybox symiink.

[dicorer]

lsMMod?

[Jason W]

lsmod typo.  Fixed.

[dicorer]

are you interested in my reports? yes or not?

[Jason W]

Yes, I just fixed the last one which was a misnamed file.

[dicorer]

Hi,
allright then.

Coming back, please see that, even if it looks a trivial matter, I could not be.
Afaik, as for dCore init logic, lsmod is already in /bb.
Duplicating it in /bin, could (randomly) be messed up by busybox cp (as I warned before).
Thats because standard sce-import always imports kmod pkg.
So it could end up with a random setup, where lsmod could be resolved either as /bb, as kmod, as busybox sym or broken link.
Of course, it depends on the application which calls it, on PATH, and so on.
Asof, btw, kmod is one of the many pkgs I exclude from import, with my mod.
ok?

[Jason W]

I believe /bin/lsmod was in base as some apps expect it there, like /bin/bash for bash.  But /bin/lsmod already existing as a symlink will prevent the one from kmod being installed there.

Here is where the startup scripts come into play.  I will make kmod remove that busybox symlink, and replace it with the /bin/lsmod from kmod.  That way busybox lsmod until kmod is installed. 

Kmod is not always imported as a dep for me.  The dependency list for the file package:


file
gcc-4.9-base
libc6
libgcc1
libmagic1
zlib1g
/tmp/.pkglist (END)

[dicorer]

Hi,

Here is where the startup scripts come into play.  I will make kmod remove that busybox symlink, and replace it with the /bin/lsmod from kmod.  That way busybox lsmod until kmod is installed.

I was talking in general, lsmod was just the one example passing by...
Anyway, if I'm understanding well, you are going to "invert" the SCEs import functional logic... isn't it a bit dangerous?
Afaik, now it works such as, links and files already in place are NOT substituted with new ones coming from subsequent SCEs - first which comes takes the place (excluding random cp glitches)
What you want to do is inverting that behavior - the last coming always kicks out the others, isn't it?
Well, I modded for a slightly more conservative strategy, you interested?

Kmod is not always imported as a dep for me.  The dependency list for the file package:

when I say always, I meant kmod and any other pkgs are always dragged in, if ubuntu dependency index says so.
Only "advanced" users can mod that out.