Mailing List Archive: github question

github question

zdravko.balorda at siix

Sep 1, 2010, 4:21 AM

Post #1 of 7 (3360 views)

Hi,
I am about to upgrade to 2.0 and also would like to start
working on briolage github repository.
I've got an account, and bricolage git "working" copy in
a local directory. From here I can do make install or
make upgrade and install bricolage. But here I have a
question: make install or upgrade would do its job in
bricolage directory, in my case /usr/local/bricolage.
I'll have two copies od bricolage, github repository and
the installation directory.

Now, any changes should be done twice? This seems wrong.
Any advice on this?

Regards, Zdravko

Re: github question [ In reply to ]

paulo at digitalcraftsmen

Sep 1, 2010, 7:06 AM

Post #2 of 7 (3284 views)

I installed it and then removed the installed lib and comp directories
and symlinked them to the lib and comp directories in the repository.
That worked quite well from what I remember. You have to restart
bricolage when you change the libraries but you can turn off the mason
caching I think which meant the comp dir was being loaded on the fly.

regards,

Paul

On 01/09/2010 12:21, Zdravko Balorda wrote:
>
> Hi,
> I am about to upgrade to 2.0 and also would like to start
> working on briolage github repository.
> I've got an account, and bricolage git "working" copy in
> a local directory. From here I can do make install or
> make upgrade and install bricolage. But here I have a
> question: make install or upgrade would do its job in
> bricolage directory, in my case /usr/local/bricolage.
> I'll have two copies od bricolage, github repository and
> the installation directory.
>
> Now, any changes should be done twice? This seems wrong.
> Any advice on this?
>
> Regards, Zdravko
>
>

Re: github question [ In reply to ]

lannings at gmail

Sep 1, 2010, 8:36 AM

Post #3 of 7 (3292 views)

Symlink 'bin', too.

On Wed, Sep 1, 2010 at 4:06 PM, Paul Orrock <paulo@digitalcraftsmen.net> wrote:
> I installed it and then removed the installed lib and comp directories and
> symlinked them to the lib and comp directories in the repository. That
> worked quite well from what I remember. You have to restart bricolage when
> you change the libraries but you can turn off the mason caching I think
> which meant the comp dir was being loaded on the fly.
>
> regards,
>
> Paul
>
> On 01/09/2010 12:21, Zdravko Balorda wrote:
>>
>> Hi,
>> I am about to upgrade to 2.0 and also would like to start
>> working on briolage github repository.
>> I've got an account, and bricolage git "working" copy in
>> a local directory. From here I can do make install or
>> make upgrade and install bricolage. But here I have a
>> question: make install or upgrade would do its job in
>> bricolage directory, in my case /usr/local/bricolage.
>> I'll have two copies od bricolage, github repository and
>> the installation directory.
>>
>> Now, any changes should be done twice? This seems wrong.
>> Any advice on this?
>>
>> Regards, Zdravko
>>
>>
>
>

Re: github question [ In reply to ]

phillip at communitybandwidth

Sep 1, 2010, 8:52 AM

Post #4 of 7 (3284 views)

On 2010-09-01, at 4:21 AM, Zdravko Balorda wrote:

>
> Hi,
> I am about to upgrade to 2.0 and also would like to start
> working on briolage github repository.
> I've got an account, and bricolage git "working" copy in
> a local directory. From here I can do make install or
> make upgrade and install bricolage. But here I have a
> question: make install or upgrade would do its job in
> bricolage directory, in my case /usr/local/bricolage.
> I'll have two copies od bricolage, github repository and
> the installation directory.
>
> Now, any changes should be done twice? This seems wrong.
> Any advice on this?

http://blogs.perl.org/users/phillip_smith/2010/07/bricolage-cms-hacking-made-easy.html

--
Phillip Smith // Simplifier of Technology // COMMUNITY BANDWIDTH
www.communitybandwidth.ca // www.phillipadsmith.com

Re: github question [ In reply to ]

david at kineticode

Sep 1, 2010, 8:55 AM

Post #5 of 7 (3293 views)

On Sep 1, 2010, at 7:06 AM, Paul Orrock wrote:

> I installed it and then removed the installed lib and comp directories and symlinked them to the lib and comp directories in the repository. That worked quite well from what I remember. You have to restart bricolage when you change the libraries but you can turn off the mason caching I think which meant the comp dir was being loaded on the fly.

Use `make dev` to have this done for you automatically. Deets at the link from Phillip.

Best,

David

Re: github question [ In reply to ]

zdravko.balorda at siix

Sep 1, 2010, 10:50 PM

Post #6 of 7 (3283 views)

David E. Wheeler wrote:
> On Sep 1, 2010, at 7:06 AM, Paul Orrock wrote:
>
>> I installed it and then removed the installed lib and comp directories and symlinked them to the lib and comp directories in the repository. That worked quite well from what I remember. You have to restart bricolage when you change the libraries but you can turn off the mason caching I think which meant the comp dir was being loaded on the fly.
>
> Use `make dev` to have this done for you automatically. Deets at the link from Phillip.

Excellent! I am sitting on my fingers while preparing for this big switch. It involves
everything from 1.10.4 to bricolage 2, apache 2.2 and postgres and perl update. And my
own hacks regarding slovene translation.

Regards, Zdravko

Re: github question [ In reply to ]

david at kineticode

Sep 2, 2010, 9:58 AM

Post #7 of 7 (3283 views)

On Sep 1, 2010, at 10:50 PM, Zdravko Balorda wrote:

> Excellent! I am sitting on my fingers while preparing for this big switch. It involves
> everything from 1.10.4 to bricolage 2, apache 2.2 and postgres and perl update. And my
> own hacks regarding slovene translation.

Commit them to a branch in your GitHub fork and send a pull request!

Best,

David