keremet/mkimage-profiles
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ccf3b2220a
mkimage-profiles/doc/assumptions.txt

47 lines
2.7 KiB
Plaintext
Raw Normal View History

added asciidoc support
2012-10-31 01:21:23 +04:00
*Предположения фрагментов кода об окружении*
doc/assumptions.txt: specify minimal gmake version From what I've read so far, most of the code should run on 3.80; there seem to have been some bits that are dependent on 3.81 features, but there is not a bit that depends on 3.82+ features so far.
2012-02-18 11:46:03 +04:00
NB: пути приводятся от верхнего уровня; проект в целом предполагает
docs update Status updates and readability tweaks all over the place.
2012-04-02 19:13:14 +04:00
ALT Linux 6.0+ и GNU make 3.81 (на которых и разрабатывается),
но может быть портирован вместе с mkimage.
docs: minor updates doc/variables.txt was missing the already-existing BUILDLOG variable description, and ARCHES got added during multi-target toplevel rewrite. Other minor fixes come as appropriate.
2012-01-02 19:52:48 +04:00
added asciidoc support
2012-10-31 01:21:23 +04:00
* lib/report.mk
** ожидает, что каждая подлежащая трассированию цель каждого
initial target tracing support and reporting The purpose is being able to examine particular target interdependency graph for a given image having been configured to avoid convoluted dependencies (loops in particular). The implementation is based on SHELL hook hint by John Graham-Cumming: http://cmcrossroads.com/ask-mr-make/6535-tracing-rule-execution-in-gnu-make
2012-03-19 15:42:10 +04:00
makefile при сборке конфигурации образа содержит непустой
recipe -- хотя бы "; @:" -- т.к. зависит от запуска $(SHELL)
added asciidoc support
2012-10-31 01:21:23 +04:00
** характерный признак пропуска -- разрыв графа (report-targets.png)
initial target tracing support and reporting The purpose is being able to examine particular target interdependency graph for a given image having been configured to avoid convoluted dependencies (loops in particular). The implementation is based on SHELL hook hint by John Graham-Cumming: http://cmcrossroads.com/ask-mr-make/6535-tracing-rule-execution-in-gnu-make
2012-03-19 15:42:10 +04:00
added asciidoc support
2012-10-31 01:21:23 +04:00
* pkg.in/lists/Makefile
** ожидает, что названия пакаджлистов указываются в переменных
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
вида *_LISTS, и копирует в генерируемый профиль только их
added asciidoc support
2012-10-31 01:21:23 +04:00
** если задать имя файла пакаджлиста непосредственно в Makefile
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
субпрофиля, он не будет скопирован
added asciidoc support
2012-10-31 01:21:23 +04:00
** характерное сообщение об ошибке:
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
E: Couldn't find package
added asciidoc support
2012-10-31 01:21:23 +04:00
* features.in/stage2/stage1/scripts.d/02-kdefault
* features.in/stage2/stage1/scripts.d/03-test-kernel
* sub.in/stage1/Makefile
** ожидают, что в stage1 попадёт строго одно ядро сообразно
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
явному указанию в STAGE1_KFLAVOUR (либо последнее указанное
в KFLAVOURS)
added asciidoc support
2012-10-31 01:21:23 +04:00
** если добавить какой-либо kernel-image в STAGE1_PACKAGES*,
stage2 based live subprofiles, updated docs - introduced generic stage2 subprofile (non-standalone) - ported installer and rescue over to stage2/{install2,rescue} - initial stage2/live (needs more work for sure) - use make-initrd-propagator - updated and somewhat extended doc/ NB: mind #26133, #26134
2011-08-20 13:55:05 +04:00
результат может быть неожиданным
added asciidoc support
2012-10-31 01:21:23 +04:00
** вероятная ошибка: незагрузка полученного squashfs
* features.in/install2/install2/stage2cfg.mk
* features.in/live/live/stage2cfg.mk
* features.in/rescue/rescue/stage2cfg.mk
* features.in/syslinux/cfg.in/15live.cfg
* features.in/syslinux/cfg.in/20install2.cfg
* features.in/syslinux/cfg.in/80rescue.cfg
* features.in/syslinux/scripts.d/20-propagator-ramdisk
** ожидают, что названия squashfs-образов второй стадии инсталятора,
test-based ramdisk size for live squashfs images Implementation based on m-p-d::profiles/scripts.d/03-syslinux (but heavily modified for m-p of course)
2011-08-22 22:37:21 +04:00
livecd и спасательной системы соответственно altinst, live и rescue
official {distro,ve}/* support This is quite a large-scale change since mkimage-profiles got used to baking distributions over the last year, and virtual environments are quite different, so e.g. image.in/Makefile had to be split in two with the main part of it moved into features.in/iso/lib/. Short overview: - features.in/Makefile: lib/ support (supporting VE images requires dynamic modifications to image.in/Makefile before starting the build; the most natural way to achieve that seems to use features mechanism along with makefile include dir) - packaging format related part moved into features.in/pack (should be better prepared for diversity either) - features.in/iso renamed to features.in/build-distro - features.in/ve renamed to features.in/build-ve + NB: these could not be merged as e.g. features.in/build due to completely different script hooks - lib/image.mk renamed to lib/build.mk - image, config, log postprocessing moved downstream - added a sort of a topping in the form of lib/sugar.mk - assorted style fixups (like ifeq usage) - clean.mk: reliability fix (the problem was observed by Oleg Ivanov and me too but finally it did get the attention quantum) - reviewed, updated and extended docs + QUICKSTART: should be[come] a step-by-step guide (thanks Leo-sp50 for prodiving feedback)
2011-10-06 12:46:31 +04:00
added asciidoc support
2012-10-31 01:21:23 +04:00
* image.in/Makefile
** ожидает, что конфигурация будет в distcfg.mk (см. тж. lib/profile.mk),
official {distro,ve}/* support This is quite a large-scale change since mkimage-profiles got used to baking distributions over the last year, and virtual environments are quite different, so e.g. image.in/Makefile had to be split in two with the main part of it moved into features.in/iso/lib/. Short overview: - features.in/Makefile: lib/ support (supporting VE images requires dynamic modifications to image.in/Makefile before starting the build; the most natural way to achieve that seems to use features mechanism along with makefile include dir) - packaging format related part moved into features.in/pack (should be better prepared for diversity either) - features.in/iso renamed to features.in/build-distro - features.in/ve renamed to features.in/build-ve + NB: these could not be merged as e.g. features.in/build due to completely different script hooks - lib/image.mk renamed to lib/build.mk - image, config, log postprocessing moved downstream - added a sort of a topping in the form of lib/sugar.mk - assorted style fixups (like ifeq usage) - clean.mk: reliability fix (the problem was observed by Oleg Ivanov and me too but finally it did get the attention quantum) - reviewed, updated and extended docs + QUICKSTART: should be[come] a step-by-step guide (thanks Leo-sp50 for prodiving feedback)
2011-10-06 12:46:31 +04:00
а лог сборки -- в build.log (см. тж. lib/log.mk); альтернативой было
бы пробрасывание переменных с полным путём ради единственного места
Reference in New Issue Copy Permalink