On 5/22/21 4:48 PM, Bill Arlofski via Bacula-users wrote: > On 5/22/21 12:49 PM, Phil Stracchino wrote: >> >> I'm about to try this out. But in the meantime, one minor quibble: >> Would you consider renaming the git file and tld to, say, bacula-report >> so that it does not have a directory name collision with the Bacula git >> repo? > > Hi Phil, > > I don't understand how a 'bacula' repo in my account can collide with a > 'bacula' repo in another account. I'd be happy to > rename it (if that is possible to do on Github), and if it is actually > necessary.
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. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
