7 Jan
2010
7 Jan
'10
10:45 p.m.
Does that mean I should revert the changes I made to Magritte-Tests or save
the latest version of Pier-Tests? I now realise their value for merging,
though the problem at the moment is that if you inadvertently load
Pier-Tests you'll end up with load errors, which at least for me was
initially off-putting.
2010/1/7 Julian Fitzell <jfitzell(a)gmail.com>
I just check my image and the same should be true of
Magritte-Tests as of
Pier-Tests (ie. I split the package into several sub-packages and thus the
original all-encompassing package is now obsolete).
Julian
On Thu, Jan 7, 2010 at 12:34 PM, Nick Ager <nick.ager(a)gmail.com> wrote:
I've saved the merged packages into pier2 and
magritte2. When I merged
magritte I updated Magritte-Tests (the super package?) as well as
Magritte-Tests-Model. For pier I only updated Pier-Tests-Model *not*
Pier-Tests, but it makes sense to me to update Pier-Tests as well. Should I.
I'll now try to loading all into a clean seaside 3.0a5 image.
2010/1/7 Lukas Renggli <renggli(a)gmail.com>
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
[...]
I guess Julian has to comment on that, but to me it sounds good :-)
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
What's the purpose of the Magritte-Model,
Magritte-Seaside and
Magritte-Tests
packages in the pier2 repository? I used the
packages in the magritte2
repository.
Hope that was the plan.
@Julian: Should these versions be moved or deleted?
I'm about the save the merged code, but when
I try I get an Error:
HTTP1.1
401 Unauthorized
Accidentally the Magritte repository didn't had public write
permissions. I changed that.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki