View Single Post
Posts: 245 | Thanked: 915 times | Joined on Feb 2012
#1030
Originally Posted by Creamy Goodness View Post
Cool, okay, well I had to break the compatibility with PR 1.2 because I'm not smart enough to have the kernel modules install in the correct folder depending on whichever kernel you have. The only problem with that is if you are stuck on PR 1.2 for some reason you're gonna get the message popping up saying there's a new version but you won't be able to install it.
I just overwrote the file on my server again with another that should have the version string fixed internally too.
If you didn't sort this out already, I'd strongly suggest simply installing the module files twice - once into each kernel module directory. It's important that it not break during an upgrade from PR1.2 to PR1.3, which is what will happen if you install into only one directory.

The best approach IMO would be to install into one of the version directories, then make a hard link using ln in the postinst script before you depmod. Make sure to delete the hard link using rm in the postrm script, again before depmod. That way, only one copy of the files takes up space, but it works no matter what.

Of course, going PR1.3-only is a legitimate option - just make sure the dependencies are set up so that it can't be installed on PR1.2.
 

The Following 2 Users Say Thank You to itsnotabigtruck For This Useful Post: