Re: rakudo.org outdated?
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 nothing broke in an update? -- Darren Duncan I wrote automated tests for GNU+Linux using GitLab CI, which are being introduced in this release. However, I can't "test" making a Windows or Mac installer, and then test if they also work. I have no idea how installers for either of these platforms are made, and I also don't think I can use GitLab CI for either of those platforms. Last I recall, there was no Mac installer for Rakudo Star at all, nor was there any need for one. The compiled project is simply in a zip file which the end-uaer unzips and then the resulting folder is ready to use as is. Don't know about Windows. If anything, on the Mac, having an installer has always been a misfeature, and most applications don't have one. -- Darren Duncan
Re: rakudo.org outdated?
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 automated tests for GNU+Linux using GitLab CI, which are being introduced in this release. However, I can't "test" making a Windows or Mac installer, and then test if they also work. I have no idea how installers for either of these platforms are made, and I also don't think I can use GitLab CI for either of those platforms. -- With kind regards, Patrick Spek www: https://www.tyil.nl/ mail: p.s...@tyil.nl pgp: 1660 F6A2 DFA7 5347 322A 4DC0 7A6A C285 E2D9 8827 social: https://soc.fglt.nl/tyil git:https://gitlab.com/tyil/ pgpfL0yxWoELx.pgp Description: OpenPGP digital signature
Re: rakudo.org outdated?
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 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 view of the recent renaming of the language. I agree with you, especially the "good" part. Since Rakudo Star has to work for more people than just me, I'm a little hesitant to move quickly with it. I can't test it on Mac or Windows, for instance, but there are users on both platforms, and having a good but old release is probably better for them than new but broken. However, if the community would rather I mark the current -rc1 as a proper release, I can do that too. I just don't want to harm the community at large. And, by the way, more generally, having a nine-month-old release to offer on the main download site looks quite bad anyway. It's not you, but something must be wrong in the process. It used to be on a three month interval, and I'd like to go to a two or three month interval myself as well. I can try to make that happen once I know for certain that the current release process works.
Re: OT: Git Hub repositories
On Sat, Jan 4, 2020 at 18:14 ToddAndMargo via perl6-users < perl6-users@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 unless you typically use modules directly > > from their repos without installing them—which is a bad practice you > > should avoid, particularly if you’re a module author. > > > > This is the confusion I was trying to get around: > > In my WinMount.pm6 module, I import three of my other modules: > > use NativeConstants; > > use WinMessageBox :WinMsg; > > use WinReg :WinReadRegKey; > I don’t see why that needs to be confusing—lots of modules (in both the language and the publishing senses) import other modules (in either sense) all the time. If you take advantage of $PERL6LIB and its ilk by assuming an on-disk location, or hardcode a `use lib`, of course you’ll get into trouble. That’s why it’s best to use proper tooling so you can “make install”. (This also lets you test changes in isolation, even if you have edits in progress simultaneously in several repos whose products depend on each other.)
Re: OT: Git Hub repositories
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 practice you should avoid, particularly if you’re a module author. This is the confusion I was trying to get around: In my WinMount.pm6 module, I import three of my other modules: use NativeConstants; use WinMessageBox :WinMsg; use WinReg :WinReadRegKey;
Re: OT: Git Hub repositories
On 2020-01-04 14:30, Simon Proctor wrote: I go with one repository per module. Thank you!
Re: OT: Git Hub repositories
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 language concepts > 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 a module author. > > On Sat, Jan 4, 2020 at 17:30 Simon Proctor > wrote: > >> I go with one repository per module. >> >> On Sat, 4 Jan 2020, 21:16 ToddAndMargo via perl6-users, < >> perl6-users@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 place them >>> all in the same repository? What would be the best for >>> sharing with folks on this list? >>> >>> Many thanks, >>> -T >>> >>> -- >>> ~ >>> When we ask for advice, we are usually looking for an accomplice. >>> -- Charles Varlet de La Grange >>> ~ >>> >>
Re: OT: Git Hub repositories
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 a module author. On Sat, Jan 4, 2020 at 17:30 Simon Proctor wrote: > I go with one repository per module. > > On Sat, 4 Jan 2020, 21:16 ToddAndMargo via perl6-users, < > perl6-users@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 place them >> all in the same repository? What would be the best for >> sharing with folks on this list? >> >> Many thanks, >> -T >> >> -- >> ~ >> When we ask for advice, we are usually looking for an accomplice. >> -- Charles Varlet de La Grange >> ~ >> >
Re: OT: Git Hub repositories
I go with one repository per module. On Sat, 4 Jan 2020, 21:16 ToddAndMargo via perl6-users, < perl6-users@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 place them > all in the same repository? What would be the best for > sharing with folks on this list? > > Many thanks, > -T > > -- > ~ > When we ask for advice, we are usually looking for an accomplice. > -- Charles Varlet de La Grange > ~ >
OT: Git Hub repositories
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 -- ~ When we ask for advice, we are usually looking for an accomplice. -- Charles Varlet de La Grange ~
Re: Working at FOSDEM
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-users@perl.org> wrote: > 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 tell them about Raku and its advantages. > > Please let me know if somebody wants to join. > > > > Regards > > > > -- > > Andrew Shitov > > __ > > a...@shitov.ru | http://shitov.ru > > I am planning to be in Brussels for FOSDEM, and I can more than likely > spend some time at the Raku table! > > -- > With kind regards, > > Patrick Spek > > > www: https://www.tyil.nl/ > mail: p.s...@tyil.nl > pgp: 1660 F6A2 DFA7 5347 322A 4DC0 7A6A C285 E2D9 8827 > > social: https://soc.fglt.nl/tyil > git:https://gitlab.com/tyil/ > -- Andrew Shitov __ a...@shitov.ru | http://shitov.ru
Re: Working at FOSDEM
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 tell them about Raku and its advantages. > Please let me know if somebody wants to join. > > Regards > > -- > Andrew Shitov > __ > a...@shitov.ru | http://shitov.ru I am planning to be in Brussels for FOSDEM, and I can more than likely spend some time at the Raku table! -- With kind regards, Patrick Spek www: https://www.tyil.nl/ mail: p.s...@tyil.nl pgp: 1660 F6A2 DFA7 5347 322A 4DC0 7A6A C285 E2D9 8827 social: https://soc.fglt.nl/tyil git:https://gitlab.com/tyil/ pgp8ttbzloy4O.pgp Description: OpenPGP digital signature
Re: rakudo.org outdated?
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 view of the > recent renaming of the language. I agree with you, especially the "good" part. Since Rakudo Star has to work for more people than just me, I'm a little hesitant to move quickly with it. I can't test it on Mac or Windows, for instance, but there are users on both platforms, and having a good but old release is probably better for them than new but broken. However, if the community would rather I mark the current -rc1 as a proper release, I can do that too. I just don't want to harm the community at large. > And, by the way, more generally, having a nine-month-old release to > offer on the main download site looks quite bad anyway. It's not you, > but something must be wrong in the process. It used to be on a three month interval, and I'd like to go to a two or three month interval myself as well. I can try to make that happen once I know for certain that the current release process works. -- With kind regards, Patrick Spek www: https://www.tyil.nl/ mail: p.s...@tyil.nl pgp: 1660 F6A2 DFA7 5347 322A 4DC0 7A6A C285 E2D9 8827 social: https://soc.fglt.nl/tyil git:https://gitlab.com/tyil/ pgpnMVpUiELo7.pgp Description: OpenPGP digital signature
