Hi All, I'm using oscar 5.0, but I'm told the repo-update and relevent subroutine scripts haven't changed in over a year, so this should still be valid in 5.1.
I did some poking around within the script, and from what I can tell the script only determines whether or not the package versions are identical or not. I am definitely not fluent in perl (yet), but there doesn't seem to be any distinction between a newer or older package version. If I'm wrong and missed this "lesser than/greater than" logic somewhere in the routines, my mistake :/ The reason this particular topic is of interest to me is efficiency. When I first updated my local fedora repo using the script, I used the --rmdup flag to remove old versions of packages. If I now want to periodicaly check online repo's for updates and such, I'd like to avoid re-downloading the old versions of packages I already downloaded and deleted the previous times. I understand if might be a hefty task to modify the algorithm to be able to do what I ask without a standard system of package nomenclature, but perhaps an alternative might be worth exploring. I'm assuming it wouldn't be too difficult to have the script log which package names and version it deleted when the --rmdup option was invoked. Then during future repo updates, it would be a simple process of comparing this already-deleted-packages list to the to-be-downloaded list and not downloading the matches. Thoughts? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
