Hi, Le vendredi 12 juillet 2024 à 11:47 AM, Simon Tournier <zimon.touto...@gmail.com> a écrit :
> > > Hi, > > On Thu, 11 Jul 2024 at 15:55, "Sebastien Rey-Coyrehourcq" > sebastien.rey-coyrehou...@univ-rouen.fr wrote: > > > Entry-point is a common way to install/link package as > > plugin. Even if my homemade package mkdocs-material is well installed > > and contain the entry-point.txt into dist-info/entry_points.txt that > > doesn't work. > > > How is the entry-point installed? Have you added a phase that run some > “pip” trick? > No tricks with pip in my actual scm, i only use `pyproject-build-system` which parse pyproject.toml of mkdocs & mkdocs-material (https://github.com/squidfunk/mkdocs-material/blob/master/pyproject.toml#L77). I read a little more the builder src and i found there is something about entry-points finally : https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/pyproject-build-system.scm#n284 But when i run =pip list= after running =guix shell -m mkdocs-material.scm= neither mkdocs or mkdocs-material packages are listed by pip ... I miss something, after building the package with pyproject-build-system i also need to install it manually from /gnu/store/xxx with =pip install= ? Perhaps my problem is more that than entry-points ? The mkdocs-material.scm : https://paste.debian.net/1323079/ Best regards, SR > Cheers, > simon
