myDSL Extensions (deprecated) :: post install

NOT TESTED

post_install.dsl

Testers welcome... I'm going to change my packages to work with this and see what happens... If you're a package maintainer and want to give it a run for the money, feel free...

Please report any issues or further thoughts or considerations. :-)

no, it doesn't do anything by itself... it's just the infrastructure to support packages having post-installs

I think you're making this much more complicated than it needs to be. 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.

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. If it works fine by adding a few lines to mydsl-install, i'm completely satisfied with that. The above runs a script after an application is installed (if the script is included in the package), and that's all i care about. I like the way myDSL works now, so i have no intention of involving myself in a rewrite

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.

Directory names i don't care about, especially if they are just tmp directories. As long as a filename doesn't include a space or some other stupid character, i really don't care what the name is.

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.

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...

i filled out my application and took the beta-tester job. yyyc514's four dsls are semi-functional together, although skippy locks up X and keyboard. Also, I couldn't get X to load properly until i dug around in .xinitrc and found that it was unable to make it's temp file in /tmp, which seems odd to me because it succeeds a few lines later making one for ssh-agent. Anyhow the obvious fix was just to point the mktemp line to /home/dsl/ as i knew that was writable, and everything came up fine. the post-install for gtk2-small worked fine as well, without a hitch.
mikshaw, i wanted to test your version too, i was given a 403 Permission Denied when trying to wget it. Would be happy to try again, im in irc 24/7

I think the xfce.dsl is an awesome contribution and the idea of a post-install script as well...glad to help further DSL, if all i can contribute atm is testing, glad to do that!

Next Page...
original here.