{"push_id":1548657561,"size":10,"distinct_size":9,"ref":"refs/heads/yem/fs","head":"43d3de41840b520b062e266da3d2b93803e7a752","before":"0f84c6eeb1e3533ff53b4f0a6c4e420682f8fb48","commits":[{"sha":"cc8c12345cf2ff6e154845f89d1ba65ea2bd3f49","author":{"name":"Baruch Siach","email":"59df7fddff988cc9cb1401c5f741eac8238ced89@tkos.co.il"},"message":"ddrescue: fix target build\n\nddrescue is not an autotools package. Convert to generic package to make\nit build correctly for target architecture.\n\nCc: Peter Seiderer <ps.report@gmx.net>\nSigned-off-by: Baruch Siach <baruch@tkos.co.il>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/cc8c12345cf2ff6e154845f89d1ba65ea2bd3f49"},{"sha":"b39737ddd55525a46a5a0acc3c5841f30c6d6fa8","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"core: sort packages and eliminate duplicates before building\n\nCurrently, enabling more than one filesystem image will make\n'show-targets' list a few host packages more than once.\n\nThis is because all filesystem images add the same set of\nhost-packages to their dependencies, which are then added as-is\nto the package list.\n\nThus, host-fakeroot, host-makedevs and, if needed, host-mkpasswd will\nappear as many times as there are filesystem images enabled.\n\nFix that by sorting the package list, thus eliminating duplicates from\nthat list.\n\nFurthermore, and even though we're already sorting packages by scanning\nthe .mk file in alphabetical order (because we $(sort) them), sorting\nthe list itself will further guarantee the build order, thus enhancing\nreproducibility (and $(sort ...) is not dependent on the locale, it\nalways sorts with the C locale).\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nCc: Peter Korsgaard <jacmet@uclibc.org>\nReviewed-by: Romain Naour <romain.naour@gmail.com>\n\n---\nChanges v1 -> v2:\n  - fix typo in comment","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/b39737ddd55525a46a5a0acc3c5841f30c6d6fa8"},{"sha":"50c0ccc23e53edcb6c4d3fd3e89e0db1ae05895d","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"linux: split overly-long dependency line for readability\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nReviewed-by: Romain Naour <romain.naour@gmail.com>\n\n---\nThis is going to be useful to better understand the initramfs patch\ncoming next.","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/50c0ccc23e53edcb6c4d3fd3e89e0db1ae05895d"},{"sha":"4a8dcd518ad2bd470f20525688c962886c490a53","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"linux: meddle not in the affairs of filesystems, for you are tasty with bacon\n\nCurrently, the rule to rebuild the Linux kernel with an initramfs\ndirectly depends on the filesystem image filename.\n\nThis is inherently \"bad\" from a purity point of view. linux.mk should\nnot have to delve into the fs internals.\n\nRather, make it directly depend on the \"frontal\" rule that generates the\ncpio image.\n\nDrop the comment for linux-rebuild-with-initramfs, it was misleading\n(talking about generating \"the initramfs list of files\", which is not\nwhat was done, since we use a cpio as source of initramfs, not a list of\nfiles).\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nCc: Romain Naour <romain.naour@openwide.fr>\n\n---\nChanges v2 -> v3:\n  - use $(LINUX_DIR) instead of $(@D) since there's no longer any\n    directory component in the target rule  (Romain)\n\nChanges v1 -> v2:\n  - drop intermediate, unneeded stamp-file\n  - drop misleading comment\n\n---\nThis, too, will be useful for the initramfs patch coming next.","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/4a8dcd518ad2bd470f20525688c962886c490a53"},{"sha":"3573b93c93ade0ee6901a269cf7c485cb5380b2f","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"fs/initramfs: cleanup and enhance comments\n\nrootfs-initramfs is not using the generic fs infrastructure, because\nthere is virtually nothing to do to build the initramfs image: there is\nno actual image to be built to begin with.\n\nThe only purpose of rootfs-initramfs is to ensure the rootfs.cpio image\nis built and then that the Linux kernel is rebuilt with that rootfs.cpio\nas initramfs source.\n\nUsing variables of the fs infra like if it were used is misleading. It\nlooked nice as long as there was the possibility that rootfs-initramfs\nwould one day use the fs infra. But there's no way that will happen any\ntime soon.\n\nFurthermore, the linux' rule linux-rebuild-with-initramfs now already\ndepends on rootfs-cpio by itself, so we need not duplicate this\ndependency in rootfs-initramfs.\n\nStill, we want to advertise that the dependency is on rootfs-cpio, so\nwe get nice dependency graphs (and not expose the internal\nlinux-rebuild-with-initramfs rule to the users).\n\nSo, remove the variables and directly define the rules.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Romain Naour <romain.naour@openwide.fr>\nReviewed-by: Romain Naour <romain.naour@gmail.com>\n\n---\nChanges v2 -> v3:\n  - fix comment about now non-existent stamp file  (Romain)","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/3573b93c93ade0ee6901a269cf7c485cb5380b2f"},{"sha":"0cf8b0dbb158965a2f6cd75462650a1c67e861a5","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"fs/ext2: use a post-gen hook rather than a post-target rule\n\npost-target rules are probably not resilient to parallel builds, given\nthat they do not depend on the image being generated first.\n\nBeside, we already have a mechanism for running stuff after the\nfilesystem is generated, and that's called post-gen hooks.\n\nUse those hooks.\n\nNote: this basically reverts 75b6303 (rootfs-ext2: make the symlink as a\n_POST_TARGET) since we've now re-introduced post-gen hooks.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nReviewed-by: Romain Naour <romain.naour@gmail.com>","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/0cf8b0dbb158965a2f6cd75462650a1c67e861a5"},{"sha":"6f12584a965e4cc7b31f4720b0926eaa182e5c65","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"fs/cpio: use a post-gen hook rather than a post-target rule\n\nWe already have a mechanism for running stuff after the filesystem is\ngenerated, and that's called post-gen hooks.\n\nUse those hooks.\n\nNote: for cpio (and unlike ext2 previously), the dependency chain was\ncorrect, in that the post-target rule correctly depended on the image\nrule. Nonetheless, we still want to fix it for consistency.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nReviewed-by: Romain Naour <romain.naour@gmail.com>","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/6f12584a965e4cc7b31f4720b0926eaa182e5c65"},{"sha":"843cf48fcf8229b852d7412d7019f8e4dc42e5cb","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"fs/common: get rid of post-target rules\n\nThe only users of post-target rules were ext2, cpio and initramfs.\n\nOf those, ext2 and cpio were changed to use post-gen hooks, while\ninitramfs was not even using the generic rootfs infra and was fixed\nto no longer reference post-target rules.\n\nBesides, the comment in the infra was really misleading: it referenced\ninitramfs implying it was the sole user of that feature, even though\ninitramfs was not using the fs infra.\n\nFurthermore, using post-target rules was inherently broken for top-level\nparallel builds, because filesystems had to ensure the ordering by\nthemselves. Of the two real users of post-target rules (cpio and ext2),\none did enforce rules ordering (apparently correctly), while the other\nforgot to do so.\n\nWe can get rid of post-target rules altogether, now.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Arnout Vandecappelle <arnout@mind.be>\nReviewed-by: Romain Naour <romain.naour@gmail.com>","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/843cf48fcf8229b852d7412d7019f8e4dc42e5cb"},{"sha":"8f5ac885cad49ec1faa5ca2bc4107ea3b257ca9f","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"fs/common: move actions common to all filesystems to their own rule\n\nA lot of actions are common to generating the various images. Currently,\nthey are all done for each image being generated.\n\nHowever, we can do them once and for all.\n\nAlso add a sha-bang to the fakeroot script, for completeness.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nReviewed-by: Romain Naour <romain.naour@gmail.com>\n\n---\nNote: when I wrote that patch, it was only a preparatory work for something\nbigger and clever about how images are generated. However, I can't recall\nwhat it was... :-(  Yet, I believe that patch to still be valid on its own.","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/8f5ac885cad49ec1faa5ca2bc4107ea3b257ca9f"},{"sha":"43d3de41840b520b062e266da3d2b93803e7a752","author":{"name":"Yann E. MORIN","email":"5914afe43711f8d3ab584c09509bb25676fff3d1@free.fr"},"message":"[RFC] core: finalise target in its own location\n\nCurrently, after all packages have been installed into target/ , we run\na sanitising pass called 'target-finalize' on that directory, to:\n  - apply overlays\n  - remove unnecessary files (man, .h, .a ...)\n  - strip files\nas well as a few other miscellanous cleanups.\n\nThis means that target/ no longer contains only package-installed files,\nand that target-finalize might not be idempotent (i.e. sucessive runs of\ntarget-finalize may yield different results in target/ ). We're trying\npretty hard that all the internal target-finalize hooks are idempotent,\nwhether they are from the core (e.g. installing glibc locales) or\nprovided by packages (e.g. cleaning up perl files).\n\nHowever, that might not be the case for packages from br2-external for\nexample, or under complex situations where a combination of packages\ndoes not yield an idempotent sequence (quoting Wikipedia: \"a combination\nof idempotent methods or subroutines is not necessrily idempotent\"; see:\nhttps://en.wikipedia.org/wiki/Idempotence#Examples ).\n\nAddress this issue by copying target/ to a \"landing\" area where the\nfinalising takes place.\n\nThis keeps the user-visible target/ directory to contain only what\npackages have installed, helps keeping target-finalize be idempotent by\nallowing packages to provide simpler target-finalize hooks.\n\nFor simplicity for packages, we have to allow them to use $(TARGET_DIR)\neverywhere, be it in target install commands or target finalize\ncommands, without requiring them to know whether to use $(TARGET_DIR)\nor $(FINAL_TARGET_DIR). $(TARGET_DIR) always points to the directory in\nwhich to act.\n\nSo, for target-finalize, we override TARGET_DIR to point to the landing\narea. But since packages are dependencies of target-finalize, they\nwould also inherit from this override. So, we over-override TARGET_DIR\nfor packages, to point to the usual and currently used $(O)/target/\ndirectory.\n\nFinally, filesystem images are generated from that landing area, of\ncourse. Similarly, we need to override TARGET_DIR for them.\n\nSigned-off-by: \"Yann E. MORIN\" <yann.morin.1998@free.fr>\nCc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\n\n---\nNote: Thomas already expressed his dislike about that patch. Yet, for\nposterity, here it goes updated to current master and tagged as RFC...","distinct":true,"url":"https://api.github.com/repos/yann-morin-1998/buildroot/commits/43d3de41840b520b062e266da3d2b93803e7a752"}]}
{"actor":{"display_login":"yann-morin-1998"}}