I noticed something during my latest reboot

 

I see Python 2.6.6 installed and after a few lines being overwritten by python 2.6.4

 

dunno how the plugins get loaded and what their order is ? Alphabetically ??

but i know that

 

Dropbox plugin installs python 2.6.6

Plugin made by SDRS

 

<FILE Name="/boot/packages/python-2.6.6-i486-1.txz" Run="upgradepkg --install-new">
<URL>http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/d/python-2.6.6-i486-1.txz</URL>
<MD5>b8de0c9f8b89aa7b3c89823d20076867</MD5>
</FILE>

 

And Couchpotato /Sickbeard and SABNZB Plufins install Python 2.6.4

Plugins made by bennichan

 

<FILE Name="/boot/packages/python-2.6.4-i486-1.txz" Run="upgradepkg --install-new">
<URL>http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/d/python-2.6.4-i486-1.txz</URL>
<MD5>4a78fd47440409b56b24586bf856170d</MD5>
</FILE>

 

Is there a way for the plugin designers to check if the dependency is met before they randomly begin to install "older" versions

So far this didn't cause me any issues ... but i imagine it can .....

 

 

And this is why I split my install via unMenu out into multiple packages.

When packages are installed, they leave a tell tell definition in /var/log/packages.

So a plugin manager could check for prerequisites.

 

I've done that in the past in my install scripts, but I haven't delved into the while plugin design yet.

I'm just looking into creating plugins in addition to the couple unmenu packages I have out there (maraschino and moviegrabber) and I'll concur with this. We need a way of flagging something as "installed", such as having a dependency item in the package definition, potentially having a "fulfills" item in there as well (fulfills is what dependency references)