[04:00:10] | * jolau[m] has quit (Quit: Idle for 30+ days) |
[11:00:06] | * munjoma[m] has quit (Quit: Idle for 30+ days) |
[11:26:46] | <mstenta[m]> | ACTION sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/aiWgNmxOVOHIbMgo... > |
[13:06:15] | * braught[m] has joined #farmos |
[14:08:02] | <mstenta[m]> | symbioquine: I wonder if we should define our own `type` for farmOS module `composer.json` files |
[14:08:29] | <mstenta[m]> | the default for Drupal modules is `"type": "drupal-module",` |
[14:08:42] | <mstenta[m]> | but it might make sense for us to be more specific |
[14:09:05] | <symbioquine[m]> | hmmm |
[14:09:35] | <mstenta[m]> | that would make it easier, for instance, to split drupal modules into a `contrib` directory and farmOS modules into a `farm` directory - that's something i often do... although there are other ways to accomplish that |
[14:09:50] | <mstenta[m]> | just a thought that popped to mind... we can noodle on it |
[14:11:20] | <symbioquine[m]> | <mstenta[m] "that would make it easier, for i"> I thought you were already doing roughly that... https://github.com/farmOS/composer-project/blob/ecd25bac11be788bd3404278... |
[14:17:22] | <mstenta[m]> | Partly... all `drupal-modules` are being put into `modules` right now: `"web/modules/{$name}": ["type:drupal-module"],` |
[14:18:05] | <mstenta[m]> | ACTION sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/toZDvmiOuTwicXBv... > |