On 5/22/21 9:44 PM, Phil Stracchino wrote: > OK, what I mean is, suppose you have a single location where you keep > source code distributions (in my case it's /netstore/src). And I git > clone the Bacula source repository into that, and it creates > /netstore/src/bacula, and then I go to git clone your repo and it ALSO > wants to write to /netstore/src/bacula. > > That's what I meant by colliding. They use the same namespace. You > should try not to do that, it's a bad idea when it's likely that at > least some people will try to pull both. That's why I suggested making > the top-level directory name bacula-report: it's obviously connected to > Bacula, but still clearly distinct from the actual Bacula source code > itself, and gives a pretty broad hint about what's in it.
Ahhh, yes. OK. This makes sense. I checked the Github web interface earlier today and it is super simple to just change a repo's name. So, probably something I will do soon. That will also fit better if/when I add some more Bacula related scripts, each into their own repo. I will announce the name change on this list when I do. Thanks for the clarification. P.S. I worked on support for MariaDB and MySQL today. It will take a little time, but it is "in process"™ ;) Best regards, Bill -- Bill Arlofski w...@protonmail.com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
