On 9/19/17, Andy Goth <[email protected]> wrote: > On 9/19/2017 4:22 PM, BohwaZ wrote: >> The only way to avoid that is having Composer use your dist zip and have >> that zip file only contain what should be required. > > Put the ex= query parameters directly in the download links on your web > pages. When the user clicks Download, the zip or tar.gz file will > contain the appropriate subset of files. > >> In Fossil anyone could just create a make recipe to generate a proper >> ZIP file and sync it in the unversioned files instead. > > Also good.
These are both excellent choices. Suppose we did as the OP requests and provided a new setting that specifies the default value for --exclude or ex=. That would not be hard to implement. But it seems like it could lead to a subtle trap for unwary users. If one developer turns on the default ex= setting and another developer is unaware of that and goes to get a tarball, the second developer might not realize the some files had been intentionally excluded and spend a lot of time trying to track down the "bug" in Fossil. Yes, Git provides a way to have a default ex= value. But then again, Git is notorious for leaving subtle traps for tripping up unwary users. Fossil is not sinless in that regard, either, but we would at least like to be less tricky than Git, no? If having a default ex= value really is needed, perhaps it could be provided using alternative URLs - perhaps /abridgedtarball and /abridgedzip instead of /tarball and /zip. Or maybe some other prefix that is more succinct than "abridged". Maybe /exporttarball and /exportzip? -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
