Re: Creating a C/C++ team?
Hello, Is it too late to have this team having an id name 'cpp' rather than 'c++'? As a fan of regex its use of the almighty plus sign has wrankled me. Also, as an outsider Ive always considered cpp to be representative of both C and C++, rather than a subset. Thanks, Jonathan On 2024-12-05 23:35, Greg Hogan wrote: On Fri, Nov 29, 2024 at 4:35 AM Liliana Marie Prikler ... $ ./etc/teams.scm show c++ id: c++ name: C/C++ team description: C and C++ libraries and tools and the CMake build system. + Note that updates to fundamental packages are the competency of the + core-packages team. scope: + gnu/build-system/cmake.scm + gnu/build/cmake-build-system.scm + gnu/packages/c.scm + gnu/packages/cmake.scm + gnu/packages/cpp.scm + gnu/packages/ninja.scm + gnu/packages/valgrind.scm
Re: Creating a C/C++ team?
Am Fri, Dec 06, 2024 at 08:27:25AM + schrieb indieterminacy: > Is it too late to have this team having an id name 'cpp' rather than 'c++'? > As a fan of regex its use of the almighty plus sign has wrankled me. > Also, as an outsider Ive always considered cpp to be representative of both > C and C++, rather than a subset. For me, "cpp" is the "C PreProcessor", and only incidentally the file suffix for C++ files (and not for C files). Andreas
Re: Lisp assembly at 38c3
Fabio, Thanks for leading this initiative. I guess your ambitions go beyond just making London a Guix hub :) Id encourage you to mention the assembly to the TXR mailinglist: https://www.kylheku.com/txr-users/ While this Lisp flavour is lacking in numbers its designs and practices are exemplary. Fingers crossed and somebody may be able to present something at this prestigious event. On 2024-12-06 18:50, Fabio Natali wrote: Dear All, tl;dr: This is to let you know that I've registered a Lisp assembly at 38c3. I'm currently reaching out to various Lisp-related communities to see if anyone is also attending 38c3 and might be interested in joining the assembly. More context: 38c3 is the 38th edition of the Chaos Communication Congress or CCC[0], the annual hacker conference happening in Hamburg, Germany from 27th to 30th December. Roughly speaking, a Congress assembly is a space that's made available for a self-organised group, to collaborate, organise workshops, talks, etc. around a specific project or area of interest. The 38c3 Lisp assembly[1] is meant as a meeting point for Lisp aficionados of all levels as well as for the passer-by who's curious and wants to know more. I hope this will attract friends from a variety of Lisp dialects (e.g. Chicken, Clojure, Common Lisp, Emacs Lisp, Fennel, Guile, Racket) and Lisp-based projects (e.g. Emacs and Guix). I'd like to prepare a small number of activities, such as: - micro talks, - pair-programming sessions, - bug-reporting/bug-fixing/patch-review sessions. No code-of-conduct has been chosen yet but there'll be one (which can be chosen collaboratively if you like, possibly taken from or inspired by one particular Lisp project's CoC). As I'm only familiar with a small fraction of Lisp languages and projects, I'd love to hear from any fellow Lisp-minded hacker who's also planning to be at 38c3, to join forces and plan things together. If you're interested or have any question, you can: - write to ~fabionatali/lisp-at-3...@lists.sr.ht (public list[2]), or - reply to this email (make sure to CC me please), or - reach out on the Fediverse at @f...@social.coop, or - reach out on IRC at fnat at libera.chat. Have a lovely day, cheers, Fabio. PS: I'm planning to send this out to the following Lisp mailing lists: - chicken-hack...@nongnu.org - cloj...@googlegroups.com - ~technomancy/fen...@lists.sr.ht - guile-de...@gnu.org - d...@racket-lang.org - emacs-de...@gnu.org - guix-devel@gnu.org Apologies if you end up receiving multiple copies through different channels. Let me know if there's any other relevant community that I should reach out to. - [0]: https://en.wikipedia.org/wiki/Chaos_Communication_Congress - [1]: https://events.ccc.de/congress/2024/hub/en/assembly/lisp/ - [2]: https://lists.sr.ht/~fabionatali/lisp-at-38c3/ Kind regards, Jonathan
Lisp assembly at 38c3
Dear All, tl;dr: This is to let you know that I've registered a Lisp assembly at 38c3. I'm currently reaching out to various Lisp-related communities to see if anyone is also attending 38c3 and might be interested in joining the assembly. More context: 38c3 is the 38th edition of the Chaos Communication Congress or CCC[0], the annual hacker conference happening in Hamburg, Germany from 27th to 30th December. Roughly speaking, a Congress assembly is a space that's made available for a self-organised group, to collaborate, organise workshops, talks, etc. around a specific project or area of interest. The 38c3 Lisp assembly[1] is meant as a meeting point for Lisp aficionados of all levels as well as for the passer-by who's curious and wants to know more. I hope this will attract friends from a variety of Lisp dialects (e.g. Chicken, Clojure, Common Lisp, Emacs Lisp, Fennel, Guile, Racket) and Lisp-based projects (e.g. Emacs and Guix). I'd like to prepare a small number of activities, such as: - micro talks, - pair-programming sessions, - bug-reporting/bug-fixing/patch-review sessions. No code-of-conduct has been chosen yet but there'll be one (which can be chosen collaboratively if you like, possibly taken from or inspired by one particular Lisp project's CoC). As I'm only familiar with a small fraction of Lisp languages and projects, I'd love to hear from any fellow Lisp-minded hacker who's also planning to be at 38c3, to join forces and plan things together. If you're interested or have any question, you can: - write to ~fabionatali/lisp-at-3...@lists.sr.ht (public list[2]), or - reply to this email (make sure to CC me please), or - reach out on the Fediverse at @f...@social.coop, or - reach out on IRC at fnat at libera.chat. Have a lovely day, cheers, Fabio. PS: I'm planning to send this out to the following Lisp mailing lists: - chicken-hack...@nongnu.org - cloj...@googlegroups.com - ~technomancy/fen...@lists.sr.ht - guile-de...@gnu.org - d...@racket-lang.org - emacs-de...@gnu.org - guix-devel@gnu.org Apologies if you end up receiving multiple copies through different channels. Let me know if there's any other relevant community that I should reach out to. - [0]: https://en.wikipedia.org/wiki/Chaos_Communication_Congress - [1]: https://events.ccc.de/congress/2024/hub/en/assembly/lisp/ - [2]: https://lists.sr.ht/~fabionatali/lisp-at-38c3/ -- Fabio Natali https://fabionatali.com
Re: Creating a C/C++ team?
Am Donnerstag, dem 05.12.2024 um 18:35 -0500 schrieb Greg Hogan: > v2 below. Removed compiler (llvm[-meta].scm) scope and removed > "compilers" from description. > > +1 to an LLVM team or llvm[-meta].scm in the core-packages scope. > > I think cmake-build-system belongs in the C++ team scope. Our use of > cmake is rather simple, even with the enhancements collected in > #70031 (which began with a desire to parallelize tests). We should > keep cmake up-to-date without bothering core-packages. I think we can do smaller topic-branches, regardless of which team ought to do the review work. There could even be multiple teams on a particular series, to push it more quickly. > ninja.scm and valgrind.scm are essentially single package modules. > The suggested build-tools.scm, check.scm, and debug.scm are a mix. > For example, check.scm includes python-pytest among other python > packages. Not sure why these are not in python-check.scm unless there > would be circular dependencies. Given the success of the teams > workflow, should we look to divide these mixed modules by team rather > than grouping by theme? In my opinion, we shouldn't be that exclusionary w.r.t. non-C languages. Tools being written in Python historically hasn't stopped C++ users from adopting them – see Meson or Conan for some popular examples. > $ ./etc/teams.scm show c++ > id: c++ > name: C/C++ team > description: C and C++ libraries and tools and the CMake build > system. > + Note that updates to fundamental packages are the competency of the > + core-packages team. I would just shorten that to "C/C++ libraries and tools", with the CMake build system being one of said tools :) Blasting notes into the team description is imho not a good idea. > scope: > + gnu/build-system/cmake.scm > + gnu/build/cmake-build-system.scm > + gnu/packages/c.scm > + gnu/packages/cmake.scm > + gnu/packages/cpp.scm > + gnu/packages/ninja.scm > + gnu/packages/valgrind.scm Scope looks good enough, even while bikeshedding. Cheers
