Hi, I do not have a strong opinion about repositories, but I do think that the concrete loggers will be inevitably created by different people with different interests, and this setup will naturally be more suitable for different repositories.
I do have a strong opinion about baselines: The baseline problem exists already at a significant scale and is not a local one. they are too costly to maintain now, and we need to build tools anyway to handle them cheaply. Without those tools we are confined to manual work, and optimizing design around manual work is not a good direction. So, trying to optimize one project is not particularly useful. About Metacello groups: I think that in most cases using them for dependency purposes is less productive than a separate baseline because they are not reified completely, and they are also not polymorphic with baselines which makes it hard to build tools to handle them. Cheers, Doru > On May 25, 2018, at 10:50 PM, Norbert Hartl <[email protected]> wrote: > > Really?? Don‘t you think the overhead is massive compared to the gain? > > Norbert >> Am 25.05.2018 um 21:08 schrieb Tudor Girba <[email protected]>: >> >> Hi, >> >> Yes, we want to have the concrete loggers managed with separate baselines. I >> would also put them in individual repositories. >> >> Cheers, >> Doru >> >> >>> On May 25, 2018, at 5:58 PM, Denis Kudriashov <[email protected]> wrote: >>> >>> >>> 2018-05-25 17:21 GMT+03:00 Stephan Eggermont <[email protected]>: >>> Denis Kudriashov <[email protected]> >>> wrote: >>>> Hi. >>>> >>>> I was looking at Beacon again to prepare integration. Some changes was >>>> needed in baseline for better granularity. So I send pull request because I >>>> have no permissions. >>>> >>>> But now I remember that we had idea to integrate only core part of Beacon >>>> which requires MemoryLogger and TranscriptLogger. And we wanted to manage >>>> logger backends using separate baselines. So we need separate repos to have >>>> separate versioning. >>> >>> Why would you want separate baselines for that? And on top of that separate >>> repos? >>> >>> Because when you will fix or improve Beacon-SysLog you will probably do not >>> want to update Beacon-Core version which will force you to update Pharo >>> (where SysLog is not loaded). >>> >>> >>> Stephan >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> >> >> >> >> > > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."
