Source control version and Pier

[Mariano Martinez Peck]

I wanted to say bazaar not bazar haha

On Mon, Apr 20, 2009 at 5:45 PM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

>
>
> On Mon, Apr 20, 2009 at 4:45 PM, Keith Hodges <keith_hodges at yahoo.co.uk>wrote:
>
>> Mariano Martinez Peck wrote:
>> > Hi folks!
>> >
>> > I was trying to see how to manage all my code and resources of a Pier
>> > application. There are several things I must manage:
>> >
>> > 1) My library (css, js, and so on), seaside components, ...
>> > 2) External files  ( /files )
>> > 3) Pier content (trough import/export utility)
>> >
>> > For 1) I use Monticello.
>> >
>> > But I don't know how to manage 2) and 3). I tough I could have a SVN
>> > project where I can put them. So, what I should do is: export and then
>> > commit SVN.
>> My prefered solution is to use bazaar for 1, and 2, and for the image,
>> and all support files. This is because bazaar supports a lightweight
>> checkout for deployment.
>
>
> Thank you very much to both of you.
>
> It is a long time since I want to try bazar. I really hate SVN so, this is
> the perfect exuse for me to use bazar :)
>
>
>>
>> > However, I would like to have all in the same control version system.
>> > Is there a way I can do 2) and 3) in MC
>> One reason I added files support to Monticello 1.5 was for seaside
>> css/js. (yes MC can handle files, check squeak-dev announcements)
>>
>
> Do you know which verion is in Pier 1.1.1 one click image ? and in pharo ?
>
> Thanks a lot.
>
> Mariano
>
>
>>
>> Keith
>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20090420/191bb426/attachment.html>