As Pippy maintainer I wanted to know what changes do I need to make so that sugar-jhbuild generates the MANIFEST file by executing "./setup.py fix_manifest" automatically.
I agree that the MANIFEST file shouldn't be included in the repos. To cite an example, it is not present in the Read mainline-repo. Thanks, Anish Mangal On Mon, May 17, 2010 at 7:34 PM, Sascha Silbe <sascha-ml-ui-sugar-de...@silbe.org> wrote: > On Mon, May 17, 2010 at 10:52:24PM +1000, James Cameron wrote: > >> On Mon, May 17, 2010 at 11:10:56AM +0200, Sascha Silbe wrote: >>> >>> Isn't MANIFEST generated automatically by running "./setup.py >>> fix_manifest"? We should remove it from the Pippy git repo and make >>> sure sugar-jhbuild calls fix_manifest. >> >> Therefore remove also from Calculate, Hello World, Moon, Physics, and >> probably quite a few other activities. > > If these activities currently include MANIFEST in git, then yes, they should > stop doing so. Please note that I'm talking about git only, not release > tarballs or .xo's. > >> Sounds like a big change. Why do this? > > For the same reasons we're doing it for other autogenerated files. They have > a tendency to get stale (exactly what we're dealing with here) and/or cause > conflicts (see constant python-xklavier build failures [1]). > > > [1] https://buildbot.sugarlabs.org/ > > CU Sascha > > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBCgAGBQJL8U0CAAoJELpz82VMF3DaFWIIAJ0XrQhtvCI6EH4RPJvhV0sB > VZJ4MYJ2NRVi7LmGDqZ6yfDL9vxa5qTxsDRe9WBAo/urRr7f58XhRUFz2865ZJkm > qCsLRLGQ9nhZVSajQbU4HZMtL0Jjv33plz3FO1s2fNBlFkreEAUJQvFTmOChv5n3 > M3韱졩怛蘴ឧᥴ㤇풸၆䚯급ʟ쐣ꉎ嫉췺촯뚷凅➕낌� > WL6zczeHqHaSJHGhqHvapiFzel3uz3RfMeRLvboEb8dDwCuaFDVZXZAqRr28Dacj > 7WcSN9v06HJB1rkgY7VFQt傝⧖瑣᠗銾ᬠ뒮椹峞镌䲘뭆흂潘= > =99T3 > -----END PGP SIGNATURE----- > > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel