Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Product-Core
New issue 186 by
[hidden email]: Metacello toolbox proposal
http://code.google.com/p/metacello/issues/detail?id=186Hi,
in Pharo 2.0 i recently used the metacello toolbox script
createDevelopment:for:importFromBaseline:description: and noticed that it
insists on a versionstring for projects in the baseline to do its thing in
such a way, that it also fetches the used version of the project. i added
an empty versionstring to the projects in the baseline and the script did
its work nicely. then i deleted that nonsense-versionstrings again. i did
this in a project that is not my own and where the baseline is used as
bleedingEdge, hence i was obviously hesitant to add a permanent
versionstring where the original author didnt do that; probably a not
really rare scenario.
hence my question: wouldnt it make sense, if there would also be an
additional script (or just an additional boolean argument for something
like 'alwaysFetchProjectVersions:') that would do that for me?
btw snapshotcello has no problems with this scenario. im just hesitant to
use snapshotcello because of that gobbledygook it produces. if everybody
follows its example and put its own language on top of the metacello
language, then configurations become completely unreadable.
werner
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
