Dependencies between git projects ?
I normally specify my dependencies between git projects like this: BaselineOfP3 >> baselineOf: spec <baseline> spec for: #common do: [ spec baseline: 'NeoJSON' with: [ spec repository: 'github://svenvc/NeoJSON:master/repository' ]. baseline: 'ZTimestamp' with: [ spec repository: 'github://svenvc/ztimestamp:master/repository' ]. spec baseline: 'Glorp' with: [ spec repository: 'github://pharo-rdbms/glorp:master/']. spec package: 'P3' with: [ spec requires: #('NeoJSON' 'ZTimestamp') ]. spec package: 'P3-Tests' with: [ spec requires: #('P3') ]. spec package: 'P3-Glorp' with: [ spec requires: #('P3' 'Glorp') ]. spec group: 'default' with: #('P3' 'P3-Tests'). spec group: 'core' with: #('P3'). spec group: 'glorp' with: #('P3-Glorp') ] Today I (finally, duh) realised that the github:// syntax actually requires a valid GitHub user. Since I do this with all my (public) projects, it obviously works (for others too), but still, is it actually 'wrong' ? Sven
Sven Van Caekenberghe-2 wrote
is it actually 'wrong' ?
Looks okay to me. Can you say more about what you mean by âwrongâ? NB if your subprojects have metadata and your main project doesnât have to be compatible outside recent Pharo you can remove the code subfolder from those URLs and eliminate a bit of duplication ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
On 7 May 2019, at 21:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Sven Van Caekenberghe-2 wrote
is it actually 'wrong' ?
Looks okay to me. Can you say more about what you mean by âwrongâ?
With 'wrong' I mean that if you are not a GitHub user yourself, you cannot access a repository that way, you need to use https (IIUC). This seems to happen automatically by Metacello though.
NB if your subprojects have metadata and your main project doesnât have to be compatible outside recent Pharo you can remove the code subfolder from those URLs and eliminate a bit of duplication
You mean 'repository' ? I sometimes use an empty one, although it seems 'src' is the standard now.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
In Pharo settings you can set it to use HTTPS for all github: repos. Maybe on the first github authentication error it could ask whether they'd prefer to use anonymous HTTPS to connect to github. Sven Van Caekenberghe-2 wrote
On 7 May 2019, at 21:32, Sean P. DeNigris <
sean@
> wrote:
Sven Van Caekenberghe-2 wrote
is it actually 'wrong' ?
Looks okay to me. Can you say more about what you mean by âwrongâ?
With 'wrong' I mean that if you are not a GitHub user yourself, you cannot access a repository that way, you need to use https (IIUC). This seems to happen automatically by Metacello though.
NB if your subprojects have metadata and your main project doesnât have to be compatible outside recent Pharo you can remove the code subfolder from those URLs and eliminate a bit of duplication
You mean 'repository' ? I sometimes use an empty one, although it seems 'src' is the standard now.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
participants (3)
-
Paul DeBruicker -
Sean P. DeNigris -
Sven Van Caekenberghe