How to fork the debugger (GitHub)

LanX has asked for the wisdom of the Perl Monks concerning the following question:

Hi I want to fork the debugger and adjust it to my needs such that it supports a REPL and a SHELL mode.

Question: what's the most reasonable version of perl5db.pl to pick for that on github?

update

found this, which looks much better than I remembered it

https://github.com/Perl/perl5/blob/blead/lib/perl5db.pl

But how do I fork one file instead of the whole perl5 project?

Updates

Expanded title and linked "fork" for clarity

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on How to fork the debugger (GitHub)

Replies are listed 'Best First'.
Re: How to fork the debugger by Corion (Patriarch) on Jun 07, 2020 at 06:25 UTC
You cannot do that. I think there are some potential approaches: Copy `perldb.pl` into its own directory, and start a fresh git repository with it. This way you get a clean directory but lose all connection to the upstream. It is also easy to set up and understand. Importing changes from upstream will likely devolve into manually resolving diffs between bleadperl and your version. Clone the `perl` repository and ignore the rest of the files. This way, you can always resynchronize with the changes in Perl, at the cost of also synchronizing a lot of files you don't care about. Clone and then rewrite the `perl` git directory using `git filter-branch` to only transfer the history of `perl5db.pl` into the new repository. This way you keep all the file history of `perl5db.pl` and you can also periodically get a fresh version of the `perl` repository and export the `perl5db.pl` related patches to rebase your changes on it. Speak to p5p to spin off `perl5db.pl` from the core and make the CPAN version (to be released by you) upstream. This allows development to occur outside of the Perl core and the new `perl5db.pl` will then be periodically be copied into the `perl` repository.	[reply] [d/l] [select]
Re: How to fork the debugger (GitHub) by $h4X4_\|=73}{ (Monk) on Jun 07, 2020 at 13:17 UTC
You can maybe look into using `system();` this may not suite all your needs but it does fork. fork is done first and the parent process waits for the child process to exit. system perldoc	[reply] [d/l]
Re^2: How to fork the debugger (GitHub) by haukex (Archbishop) on Jun 07, 2020 at 14:22 UTC
No, fork, not fork.	[reply]
Re^3: How to fork the debugger (GitHub) by LanX (Saint) on Jun 07, 2020 at 15:10 UTC
He he, thanks. :) After I realized the ambiguity of the title I added "(GitHub)" part. Funnily it's still misunderstood... Ż\_(ツ)_/Ż Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^3: How to fork the debugger (GitHub) by perlfan (Vicar) on Jun 08, 2020 at 12:48 UTC
> No, fork, not fork. We can do that, we don't even need a reason.	[reply]
Re^4: How to fork the debugger (GitHub) by ikegami (Patriarch) on Jun 08, 2020 at 22:05 UTC


Think about Loose Coupling
	PerlMonks