Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there really a need for the two symbolic links? #49

Open
JJ opened this issue Oct 28, 2023 · 4 comments
Open

Is there really a need for the two symbolic links? #49

JJ opened this issue Oct 28, 2023 · 4 comments

Comments

@JJ
Copy link
Collaborator

JJ commented Oct 28, 2023

I've checked repo history, and can't find why they are needed. They are polluting the distro tar bundle #44, is there any functional reason for them to be there?

@Tux
Copy link
Owner

Tux commented Oct 30, 2023

The reason is easy edit. I do my work on modules from the top-level directory and vi CS<tab> is easier than vi lib/Text/CSV.rakumod (or vi li<tab>/<tab><tab>. Likewise vi *pod is easier than vi lib/Text/CSV.pod6

@JJ
Copy link
Collaborator Author

JJ commented Oct 30, 2023

But you can do that without including it in the repo, as long as you have a finite amount of different machines to work on, right?
(also, I do Control-r + a few letters like t/CS. Sometimes you don't even need that, if you did it some time ago. Plus, with Comma, any file is just a click away. Not forced to use comma, though.

@Tux
Copy link
Owner

Tux commented Oct 30, 2023

The links do not need to be in the repo. My develop folder has more files that do not need to be in git.
In perl5 world, the distro is controlled by MANIFEST, so you can have whatever you like in git and share that with other developers without anyone complaining. Raku uses the git index which imposes different ways to work that I never adapted to

@JJ
Copy link
Collaborator Author

JJ commented Oct 30, 2023

Well, it's not Raku but zef, and even in this case, it's simply gobbling up everything. I've created this issue so that it does that, or even moves to an explicit MANIFEST, but it needs a certain amount of refactoring in fez itself so no immediate solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants