[Sugar-devel] Manifests obsolescence in new Sugar versions
gonzalo at laptop.org
Fri Mar 9 12:53:19 EST 2012
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 exist, is used, if not use the list from
Another option is create a custom setup file.
I did it in the wikipedia activity, because the data files are huge,
and I use the same activity with different directories with the data for
then the logic to create the bundle is not standard.
In your case I think the best is add the files to git.
On Fri, Mar 9, 2012 at 12:21 PM, James Simmons <nicestep at gmail.com> wrote:
> 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, books
> for PGA) that I don't want in the bundle OR in git. With the MANIFEST this
> was not a problem. Without the MANIFEST I have to wonder.
> James Simmons
> On Fri, Mar 9, 2012 at 8:51 AM, Gonzalo Odiard <gonzalo at laptop.org> wrote:
>> On Fri, Mar 9, 2012 at 11:39 AM, laurent bernabe <
>> laurent.bernabe at 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.
>> No. The MANIFEST file was used only at the time of build a activity.
>> Now the build is done using the list of files in git if there are a repo,
>> or all the files if not.
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel