I think doing something à la M4, to process macro in the BaselineOf
files, but it will add confusion to the confusion. Now, in the bazaar
repo I don't have release version number either.
Le 03/04/2018 à 16:57, Thierry Goubier a écrit :
Mine as well:(
I still believe a "release" kind of scrip
2018-04-03 16:31 GMT+02:00 Hilaire :
> Probably, but my hands are already full.
Mine as well :(
I still believe a "release" kind of script could help, associated with
a project: update the baselineOf, save everything with a nice commit,
tag the commit, done.
I would need one for OSProcess, and f
Probably, but my hands are already full.
Le 03/04/2018 à 15:52, Thierry Goubier a écrit :
Couldn't you call a bazaar routine to get that information?
Writing a specific method with the version number on each release is a
bit of a pain, to have practised that before.
Unless you write a release
2018-04-03 15:25 GMT+02:00 Hilaire :
> I don't use github. I will just use a class method returning a version
> number.
Couldn't you call a bazaar routine to get that information?
Writing a specific method with the version number on each release is a
bit of a pain, to have practised that before.
I don't use github. I will just use a class method returning a version
number.
Le 03/04/2018 à 14:14, Thierry Goubier a écrit :
Normally, you should do it via the repository url. If you use tags in
your repository management and integration
into Monticello (like filetree and gitfiletree), you
Hi Hilaire,
2018-04-03 12:40 GMT+02:00 Hilaire :
> Ok, adding the package names was needed in the baseline and resolved the
> remaining errors:
>
> spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc.
>
> Now I would like to insert in the BaselineOf a version number more
> meaningfull
Ok, adding the package names was needed in the baseline and resolved the
remaining errors:
spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc.
Now I would like to insert in the BaselineOf a version number more
meaningfull than
I want to extract from 'BaselineOfDrGeo project ver
Moving the BaselineOfDrGeo out of the ConfigurationOfDrGeo package in
the file based tonel helps to get over this error. More error followed
but need to be examined.
Le 03/04/2018 à 11:42, Hilaire a écrit :
Does not work either.
PharoDebug.log is not updated with this error. I paste bellow t
Hi Thierry,
Does not work either.
PharoDebug.log is not updated with this error. I paste bellow the stack
from the debugger (but there is a no attribute values).
Hilaire
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer:
[ | references ne
Hi Hilaire,
try
Metacello new
baseline: 'DrGeo';
repository: 'tonel://', SmalltalkImage current imageDirectory
pathString, '/src';
load
Thierry
2018-04-03 10:34 GMT+02:00 Hilaire :
> Hi,
>
> I have this enclosed BaselineOfDrGeo which I think contains mostly all I
> need.
>
> How sh
10 matches
Mail list logo
