Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-10 Thread Alan Jhonn Aguiar Schwyn
I've just noticed that the manifest files are obsolete inside sugar bundle (when launching ./setup.py fix_manifest). WARNING : the fix_namifest command is obsolete The MANIFEST file is no longer used in bundles, please remove it. Another question.. If fix_manifest command

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-10 Thread Chris Leonard
On Sat, Mar 10, 2012 at 8:11 PM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I've just noticed that the manifest files are obsolete inside sugar bundle (when launching ./setup.py fix_manifest). WARNING : the fix_namifest command is obsolete                 The MANIFEST file is no

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-10 Thread Walter Bender
On Sat, Mar 10, 2012 at 8:11 PM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: I've just noticed that the manifest files are obsolete inside sugar bundle (when launching ./setup.py fix_manifest). WARNING : the fix_namifest command is obsolete                 The MANIFEST file is no

[Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread laurent bernabe
Hello everyone, I've just noticed that the manifest files are obsolete inside sugar bundle (when launching ./setup.py fix_manifest). WARNING : the fix_namifest command is obsolete The MANIFEST file is no longer used in bundles, please remove it. So : - how is file list

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread Gonzalo Odiard
On Fri, Mar 9, 2012 at 11:39 AM, laurent bernabe laurent.bern...@gmail.comwrote: Ok, I think I've understood : Before, sugar git was unable to manage files correctly without the MANIFEST, but now it is resolved. No. The MANIFEST file was used only at the time of build a activity. Now the

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread James Simmons
Gonzalo, My Read Etexts Activity includes a data file in the bundle (a catalog of e-books from PG and PG Australia) that I have never put in git because it did not seem an appropriate use of git. I did list it in the MANIFEST. There are temporary data files in my source directory (books for PG,

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread Chris Leonard
On Fri, Mar 9, 2012 at 9:51 AM, Gonzalo Odiard gonz...@laptop.org wrote: On Fri, Mar 9, 2012 at 11:39 AM, laurent bernabe laurent.bern...@gmail.com wrote: Ok, I think I've understood : Before, sugar git was unable to manage files correctly without the MANIFEST, but now it is resolved.

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread Gonzalo Odiard
In first place, would be good if you put all the files needed to create the bundle in git. Then anybody else who want experiment, modify, etc, can do it. Git works great with binary/big files too. If not, you should ask for support of MANIFEST files at build time, may be as a option. If the file

Re: [Sugar-devel] Manifests obsolescence in new Sugar versions

2012-03-09 Thread laurent bernabe
Ok, thank you, so i'll remove MANIFEST in the next commit, and keep on giving all necessary files Le 9 mars 2012 18:53, Gonzalo Odiard gonz...@laptop.org a écrit : In first place, would be good if you put all the files needed to create the bundle in git. Then anybody else who want