in reply to Multiple CPAN distributions under the same git repository?

I haven't been in such a situation, but I guess I'd go with (1). To avoid lots of jumping through hoops, I'd try to script most of the steps. For example, at work, we have lots of repositories, so I keep them all in one directory that also contains a simple shell script called forall: 
#!/bin/bash
orange=$'\e[33m'
off=$'\e[0m'


for project in */ ; do
    [[ -d "$project"/.git ]] || continue
    (
    cd "$project"
    echo "$orange$project$off" >&2
    "$@"
    )
done

[download]

so I can run commands like 

./forall git fetch upstream

[download]

So, you'd fix the code of each repository, and than just run a script to run all the tests, prepare distributions, etc.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

[download]

Replies are listed 'Best First'.
Re^2: Multiple CPAN distributions under the same git repository?
by Dallaylaen (Chaplain) on Nov 13, 2018 at 08:33 UTC

    Thank you.

    I just realized what I don't like about approach (1), which is superior in every other aspect.

    For modules' author there's virtually no difference between the three approaches. One way or another, it's going to get scripted.

    However, as a side contributor, I would prefer to know there's more than just one module. Is my bug specific to just one plugin? Am I changing some boilerplate and/or generated code? Is this change compatible with the author's tooling? And the answer to all of these is just ls.

    That said, I'm not sure whether it's just me, or there are others who feel that way.

[reply]

In Section Seekers of Perl Wisdom