Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

without knowing more this would seem the most sensible approach. the client repo, ideally, would contain next to no code at all but rather just the assembly instructions to gather which version of which library and how to configure / assemble them into the desired customized solution. Bonus of this approach is that it becomes much easier to share development with other customers (perhaps by selling new functionalities that customer A paid for for other customers that have not... yet)

Newtopian
– Newtopian

2019-04-02 13:05:24 +00:00
Commented Apr 2, 2019 at 13:05
This is exactly how the project is organized now. I thought it was clear when I wrote that clients show to default version from its composer config. Only minimal set needed to run the customization is in the client repo. There is no default repo duplication

Norgul
– Norgul

2019-04-02 20:08:18 +00:00
Commented Apr 2, 2019 at 20:08

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »