this is great! thanks Nils!

On Thu, Feb 17, 2011 at 9:02 PM, Nils Adermann <[email protected]> wrote:

> On 02/17/2011 02:39 PM, Bulat Shakirzyanov wrote:
>
>> I am not very familiar with subtree merges, but can't we say subtree
>> merge zend logger into its own repository and the submodule that? Would
>> it help?
>>
>
> Yes that is possible. You can clone just the zend log component from
>
> https://github.com/naderman/zend-log.git
>
> It is a total of *384K* when cloned and checked out. The repository is
> updated via a cron job, so feel free to use this in the symfony
> sandbox/anywhere else.
>
> I think there is no need to write a new logging library. At the same time
> if you really want to, Jordi, I don't think anyone is going to stop you
> anyway ;-) I think making use of Zend Framework in the default distributions
> of Symfony really goes a long way in showing there is no NIH-syndrome around
> here. So I am in favour of keeping it, although in this saner small
> repository size.
>
>
> For those who want to know how this works:
>
> - First get the git-subtree tool from
>    https://github.com/apenwarr/git-subtree
> - Then set up the initial repo & split.
>    $ git clone git://github.com/zendframework/zf2.git zf2
>    $ cd zf2
>    $ git remote add github-naderman [email protected]:naderman/zend-log.git
>    $ git subtree split --prefix="library/Zend/Log/" --rejoin -b zend-log
>    $ git push github-naderman zend-log:master
> - Setup a cron job doing the following:
>    $ git pull origin master
>    $ git subtree split --prefix="library/Zend/Log/" --rejoin -b zend-log
>    $ git push github-naderman zend-log:master
>
> If this was to be used for all Symfony components it could easily be
> triggered through a service hook on github instead.
>
> Cheers,
> Nils
>
>
>> Sent from my Nexus One
>>
>> On Feb 17, 2011 8:32 AM, "Yuen-Chi Lian" <[email protected]
>> <mailto:[email protected]>> wrote:
>>  > Just not rewriting.
>>  >
>>  > * Seek for 'better' logger.
>>  > * Redistribute Zend/Logger in a way. Not everything must be a git
>>  > submodule.
>>  > * Deal with it, the clone is huge, but it's just a one time pain.
>>  > * Wait for Git to improve.
>>  >
>>  >
>>  > On 2/17/2011 20:14, Lukas Kahwe Smith wrote:
>>  >> On 17.02.2011, at 13:12, Marijn Huizendveld wrote:
>>  >>
>>  >>> I agree with Yuen-Chi Lian
>>  >>>
>>  >>> Op 17 feb. 2011 om 12:55 heeft Yuen-Chi Lian<[email protected]
>> <mailto:[email protected]>> het volgende geschreven:
>>
>>  >>>
>>  >>>> Exactly.
>>  >>>>
>>  >>>> I find it ironic when we are speaking about upholding good
>> practices, we are doing something we usually avoid - reinventing the
>> wheel.
>>  >>>>
>>  >>>> It's the problem of Git for not having a sexy sparse checkout
>> solution and Zend for not packaging the libraries separately. One day,
>> when SF is no longer using Git, are you expecting to re-code some other
>> not-too-handy dependencies?
>>  >>>>
>>  >> ok .. so you disagree with the solution or the problem? and if you
>> only disagree with the solution, what is your proposed solution?
>>  >>
>>  >> regards,
>>  >> Lukas Kahwe Smith
>>  >> [email protected] <mailto:[email protected]>
>>  >>
>>  >>
>>  >>
>>  >
>>  > --
>>  > Yuen-Chi Lian | www.yclian.com <http://www.yclian.com>
>>
>>  > "I do not seek; I find." - Pablo Picasso
>>  >
>>  > --
>>  > If you want to report a vulnerability issue on symfony, please send
>> it to security at symfony-project.com <http://symfony-project.com>
>>
>>  >
>>  > You received this message because you are subscribed to the Google
>>  > Groups "symfony developers" group.
>>  > To post to this group, send email to [email protected]
>> <mailto:[email protected]>
>>
>>  > To unsubscribe from this group, send email to
>>  > [email protected]
>> <mailto:symfony-devs%[email protected]>
>>
>>  > For more options, visit this group at
>>  > http://groups.google.com/group/symfony-devs?hl=en
>>
>> --
>>
>> If you want to report a vulnerability issue on symfony, please send it
>> to security at symfony-project.com
>>
>> You received this message because you are subscribed to the Google
>> Groups "symfony developers" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/symfony-devs?hl=en
>>
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.com
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
>



-- 
*Bulat Shakirzyanov* | Software Alchemist

*a: *about.me/avalanche123
*e:* [email protected]

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to