TODO (1911B)
1 TODO 2 ==== 3 4 Low priority 5 ------------ 6 7 < > Install dependencies (it would call `mk -f $mkpklib/install.mk`) 8 - It would need dependencies db or dependencies file with the mkfiles; maybe 9 just a variable 10 11 12 Done 13 ---- 14 15 <x> Implement explicitly passing version as a parameter 16 - That would just be messy. Better to implement upgrade/downgrade. 17 - Downgrade is already there, just uninstall, remove new tarballs and 18 install again - previous tarballs will be used. 19 - Upgrade is achieved by fetch + build + install, though what is lacking is 20 uninstall before everything else. Could be wrapped into new operation. 21 - Added upgrade. 22 23 [x] Change defaults.mk: it should set variables to fixed defaults, and a new 24 file, derivatives.mk, would take into account possibly changed values of 25 variables like DESTDIR and PREFIX 26 - But then standalone lib/*.mk would have to read project's config.mk, whose 27 existance can't be assumed 28 - <| if [ -e config.mk ]; then cat config.mk; fi 29 - This is actually only an issue for build.mk? 30 31 [x] Handle legal files like the bootstrap scripts 32 - Handle them differently; since we have mkfiles here, it is possible to 33 specify legal files per-package and avoid automated search 34 35 [x] mkpk fetch 36 37 [x] Actually check SHA512 sums when installing 38 39 [x] More accurately locate packages based on name (currently, "gcc" refers also 40 to eg. directory "gcc-mlfs" if it happens to be under /src); keep fetched 41 packages in a separate database? 42 - Usage scenarios: 43 1. Packages from galeb-mkfiles 44 2. Custom local packages 45 - Version comparison? 46 - Yes. Build only the latest package, if version is 47 not explicitly given 48 - Not implementing "explicitly given" part for now (TODO) 49 50 [x] Improve recent so it takes a list of versions like testrecent; add calling 51 of recent to lib/*.mk 52 53 [x] mkpk update