On Sep 18, 2017, at 6:49 PM, BohwaZ <boh...@bohwaz.net> wrote:
I'm looking at ignoring some files when an archive (zip/tarball) is
created by Fossil.
What’s a good example where you’d want to do that?
In PHP package manager, composer (equivalent to gem in Ruby), the
complete package repository is cloned and included in the project.
This means that a bunch of tests, docs etc. will be included in every
project. This is bad as you have to download and store useless files,
plus this means that security wise you might end up with unsafe code
that can be run by the webserver. Not good.
The only way to avoid that is having Composer use your dist zip and have
that zip file only contain what should be required.
Though I think this is a problem of Composer, but its authors are
against letting the package author decide which directories/files should
be ignored: https://github.com/composer/composer/issues/1750
So I was wondering if Fossil could do the same as Git to go around that
Composer shortcoming, as that would have made my life much simpler.
But I'm not sure if I want to implement that in Fossil just because
another unrelated piece of software makes bad decisions…
In Fossil anyone could just create a make recipe to generate a proper
ZIP file and sync it in the unversioned files instead.
I might end up just setting up my own Composer repository that would
serve pre-packaged ZIP files eventually, seems more like a proper
solution.
Thanks for your help.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
