On Sat, Jan 4, 2020 at 18:14 ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> On 2020-01-04 14:40, Trey Harris wrote:
> > All the tooling (that cares at all about repos, anyway) generally expect
> > one repo per exportable product (e.g., a module).
> >
> > This shouldn’t be an issue u
On 2020-01-04 14:40, Trey Harris wrote:
All the tooling (that cares at all about repos, anyway) generally expect
one repo per exportable product (e.g., a module).
This shouldn’t be an issue unless you typically use modules directly
from their repos without installing them—which is a bad practi
On 2020-01-04 14:30, Simon Proctor wrote:
I go with one repository per module.
Thank you!
On Sat, Jan 4, 2020 at 17:40 Trey Harris wrote:
> All the tooling (that cares at all about repos, anyway) generally expect
> one repo per exportable product (e.g., a module).
>
Argh, overloaded English: I meant “publishable product”, and “CPAN-like
module”. Not export and module as in the langua
All the tooling (that cares at all about repos, anyway) generally expect
one repo per exportable product (e.g., a module).
This shouldn’t be an issue unless you typically use modules directly from
their repos without installing them—which is a bad practice you should
avoid, particularly if you’re
I go with one repository per module.
On Sat, 4 Jan 2020, 21:16 ToddAndMargo via perl6-users, <
perl6-us...@perl.org> wrote:
> Hi All,
>
> Over in Git Hub land, would you create a repository
> for each module you place on Git? Or like my modules,
> the all support/import each other, would you pla
