Version 5 Development > Plugin Design
Some suggestions to get the ball rolling
BRiT:
--- Quote from: WeeboTech on July 20, 2010, 07:47:23 PM ---As an afterthought, forgive me Brit, I might not be grasping exactly what you are trying to explain.
If I have a binary slackware package I've downloaded, and I need to doctor it up with pre/post steps.
do I replace the doinst, or add pre/post to the downloaded package.
My preference is to add something to unmodified packages, but then I might need to incorporate those mods for simplicity.
I might be missing something.
--- End quote ---
I was trying to explain that those steps to me seem like what you said in a message later on. All the steps you described seems like they should be a SlackBuild, not in an install script.
I'm thinking in this case it would be an unRAID companion package to the official slackware package. The end unRAID users would install the unRAID companion package. This companion package would be installed to /tmp/package. It could have its main code inside the doinst.sh or it could be separated out into a package.SlackBuild script that's invoked from doinst.sh. This unRAID companion package could do a wget on the official slackware package, or the official slackware package could be bundled inside the unRAID companion package. After the official slackware package is available, the companion package would do it's modifications. The last step it does is install the modified slackware package.
WeeboTech:
--- Quote from: BRiT on July 21, 2010, 10:00:57 AM ---
--- Quote from: WeeboTech on July 20, 2010, 07:47:23 PM ---As an afterthought, forgive me Brit, I might not be grasping exactly what you are trying to explain.
If I have a binary slackware package I've downloaded, and I need to doctor it up with pre/post steps.
do I replace the doinst, or add pre/post to the downloaded package.
My preference is to add something to unmodified packages, but then I might need to incorporate those mods for simplicity.
I might be missing something.
--- End quote ---
I was trying to explain that those steps to me seem like what you said in a message later on. All the steps you described seems like they should be a SlackBuild, not in an install script.
I'm thinking in this case it would be an unRAID companion package to the official slackware package. The end unRAID users would install the unRAID companion package. This companion package would be installed to /tmp/package. It could have its main code inside the doinst.sh or it could be separated out into a package.SlackBuild script that's invoked from doinst.sh. This unRAID companion package could do a wget on the official slackware package, or the official slackware package could be bundled inside the unRAID companion package. After the official slackware package is available, the companion package would do it's modifications. The last step it does is install the modified slackware package.
--- End quote ---
OK, I understand now. See my other thread.
http://lime-technology.com/forum/index.php?topic=7093.0
bubbaQ:
Downloading instead of embedding would require the end-user's unRAID server to have internet access in order to install the package.
BRiT:
--- Quote from: bubbaQ on July 21, 2010, 07:06:06 AM ---When 5.0 came out, I needed to make a single small change to the php.ini file in the unraidWeb package. It took me 15 minutes since I had not been in there for a long time. Had it been a zip file, I could have done it in 30 seconds, by just clicking on the php.ini file, editing it, and saving it and winrar or winzip would have simply updated the package with the changed file.
--- End quote ---
It also could have been done in 30 seconds if you use 7Zip on your WinOS.
WeeboTech:
--- Quote from: bubbaQ on July 21, 2010, 10:08:08 AM ---Downloading instead of embedding would require the end-user's unRAID server to have internet access in order to install the package.
--- End quote ---
Ahh the technician in us is micro managing. LOL.
I'm not worried how that package is obtained. If we have our own repository, then it will exist.
If we embed it it will exist.
I'm more concerned with managing the tedium of long install procedures that go along with these advanced packages.
If someone does or does not have internet access. I cannot worry about it.
They will need some access to start. There is no way around it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version