Hello, This is my first submission. Please let me know how I can improve forfuture packages. I followed the steps in the manual and submitted a Software Heritagerequest to pull the source code. Thank you,Kozo
Toggle quote (6 lines)> This is my first submission. Please let me know how I can improve for> future packages.>> I followed the steps in the manual and submitted a Software Heritage> request to pull the source code.
Hi Kozo, Yarn would indeed be something that would be nice to have a package for. While I guess that this might work, I think there are issues with thesource here and the lack of dependencies that make this unsuitable forGuix.
The key thing here is source. For many reasons, the packages in Guixrepresent software being built from some source material. What's being downloaded here might look like source material, but Idoubt the ~153,409 line lib/cli.js file is really the preferred form forediting the Yarn source code.
Another sign that something is up is the mismatch between the inputshere, and the dependencies in the upstream metadata . Assuming thepackage works, I'm guessing that there's a lot more than the source ofYarn within the "source" of this package. 1: https://github.com/yarnpkg/yarn/blob/master/package.json I'm hopeful that package Yarn will become possible sometime soon, but inmy mind the path forward is to get an importer working for npm, packagethe many dependencies, then attempt to package yarn. Unfortunately I don't think there's a bug that tracks this overall issuewell, although I did find a similar bug about yarn  2: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33431 Does that make sense? Thanks, Chris
The indentation is quite confusing here, I'd suggest running./etc/format-code.el on your file.
Thank you for the feedback, Christopher and Jakub. After going over what you said, this package is beyond my currentexperience. It would make sense to start getting all the dependenciesin one at a time and return to this one later. Please go ahead and close this request as I work on the buildingblocks. Thanks,Kozo
On Mon, 27 Apr 2020 08:10:28 -0600Kozo <Gitlabcanada@runbox.com> wrote:
Toggle quote (9 lines)> Thank you for the feedback, Christopher and Jakub.> > After going over what you said, this package is beyond my current> experience. It would make sense to start getting all the dependencies> in one at a time and return to this one later.> > Please go ahead and close this request as I work on the building> blocks.
Greetings, Thank you for your feedback. This package is too complex for my current experience level. The current plan of action will be to start getting all the dependencies added in and then come back to this overall package. Please close this request and we'll re-visit it in the future. Thank you,Kozo
(name . Kozo via web)(address . firstname.lastname@example.org)(address . email@example.com)
On Mon, 4 May 2020 21:28:54 +0200Kozo via web <firstname.lastname@example.org> wrote:
Toggle quote (10 lines)> Greetings,> > Thank you for your feedback. This package is too complex for my> current experience level.> > The current plan of action will be to start getting all the> dependencies added in and then come back to this overall package.> > Please close this request and we'll re-visit it in the future.
Closed with adding "-done" to the bug-number. Thanks for giving it a try and see you around with smaller packagesfirst. Björn