yyyc514
Group: Members
Posts: 41
Joined: Aug. 2005 |
 |
Posted: Sep. 04 2005,20:58 |
 |
| Quote (mikshaw @ Sep. 04 2005,15:59) | | I think you're making this much more complicated than it needs to be. |
My solution was all of like 6 lines and 1 new file (and 2 symlinks)... more complicated than your solution, yes... much more complciated than it needs to be, no. :-)
| Quote (mikshaw @ Sep. 04 2005,15:59) | | I tested the edited /etc/init.d/mydsl-install and it works fine, even for auto-loaded apps. The key for that part is to name the extension as above, 0-POSTINSTALL.tar.gz (all caps) so that it will load first before any other extension, even those beginning with "00000001AAAAA" or something like that, which is very unlikely. Not that someone couldn't name it "0-Asomething", but why would they? But maybe it should just be named 0-0.tar.gz just to make sure it will be found before anything else. |
I have NO idea how it could... mydsl-install is _not_ called during bootup as far as I can determine from source... all the installations are performed by dsl-config (and it doesn't call mydsl-install either)... so I don't know how your post-install code could even be run...
| Quote (mikshaw @ Sep. 04 2005,15:59) |
The current myDSL system is not set up to install a bunch of files at once. Each file found at boot goes through the process individually, so it might be difficult to set up a directory of post-install scripts to run all at once without making more complex changes to the system.
|
It's quite possible, and should work fine in most cases. :-) I still don't see how your solution could really work reading the code... And the loop really only happens at boot... the rest of the time it is one at a time... again, I don't see how what you wrote could work and don't see another solution except what I have proposed.
| Quote (mikshaw @ Sep. 04 2005,15:59) |
I like the way myDSL works now, so i have no intention of involving myself in a rewrite |
Again, overstatement. What I offer is far from a "rewrite" of myDSL. :-)
| Quote (mikshaw @ Sep. 04 2005,15:59) |
As far as failures go, i guess it would depend on where it fails. I would guess that if it is the post-install script failing, it would be up to the packager to make sure it works properly.
|
Of course, but sometimes a script can still fail... unless it's a pristine CD one can't guarantee what environment it's going into... did you like the idea of making them unexecutable when finished rather than deleting? I caught that in your initial idea.
| Quote | | EDIT: by making your post install *.dsl, you are putting unnecessary limits on the enduser....me, for example. I hardly ever run mkwriteable, and like to keep all apps in home and opt. |
Hmmm... It's main purpose is for dealing with .dsl packages that are subsequentially installed... so mkwritable is going to get called soon enough anyways, but I'll give this factor some thought...
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
