On 2020-01-04 5:21 p.m., Patrick Spek via perl6-users wrote:
On Sat, 4 Jan 2020 15:43:37 -0800
Darren Duncan wrote:
Isn't there typically automated test suites that can prove in a few
minutes that Rakudo works on a particular platform? Would running
this typically be good enough to show that
On Sat, 4 Jan 2020 15:43:37 -0800
Darren Duncan wrote:
> Isn't there typically automated test suites that can prove in a few
> minutes that Rakudo works on a particular platform? Would running
> this typically be good enough to show that nothing broke in an
> update? -- Darren Duncan
I wrote au
Isn't there typically automated test suites that can prove in a few minutes that
Rakudo works on a particular platform? Would running this typically be good
enough to show that nothing broke in an update? -- Darren Duncan
On 2020-01-04 11:10 a.m., Patrick Spek via perl6-users wrote:
On Fri, 3
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
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 place them
all in the same repository? What would be the best for
sharing with folks on this list?
Many thanks,
-T
--
Hi guys!
Thanks for the reaction. I passed the table to TPF, I hope they can make a
good use of it.
I will ask Stuart to contact you.
On Sat, 4 Jan 2020 at 20:12, Patrick Spek via perl6-users <
perl6-us...@perl.org> wrote:
> On Fri, 3 Jan 2020 15:43:23 +0100
> Andrew Shitov wrote:
>
> > Hi,
>
On Fri, 3 Jan 2020 15:43:23 +0100
Andrew Shitov wrote:
> Hi,
>
> On 1-2 Feb, I have secured a table at the FOSDEM exhibition area.
> Unfortunately, I found nobody who confirmed they can help at the
> location for at least 1/2 day. What needs to be done there is to talk
> to people passing by and
On Fri, 3 Jan 2020 23:28:38 +0100
Laurent Rosenfeld via perl6-users wrote:
> Hi Patrick,
>
> I'm sure you have plenty of things to do and I don't want to put too
> much pressure on you, but it would be really nice to have a good and
> more recent Rakudo Star version available, especially in vie
13 matches
Mail list logo
