Begin forwarded message:

> From: Matthew Weier O'Phinney <[email protected]>
> Date: 17. Februar 2011 23:30:54 MEZ
> To: Lukas Kahwe Smith <[email protected]>
> Cc: symfony developers <[email protected]>
> Subject: Re: [symfony-devs] Re: [Symfony2] ZF dependency
> 
> -- Lukas Kahwe Smith <[email protected]> wrote
> (on Thursday, 17 February 2011, 01:48 PM +0100):
>> 
>> On 17.02.2011, at 13:41, Johannes Schmitt wrote:
>> 
>>> Well, are we writing a logger library just because of the unused
>>> components or because ZF logger has some deficiencies? If it's just
>>> to get rid of the other components, then there are certainly better
>>> approaches... but I admit that might not be as interesting as
>>> writing an own logger library :)
>>> 
>>> IIRC Matthew also said that they would eventually provide an easier
>>> way for only using specific components.
>> 
>> The only know deficiency of Zend\Log that I am aware of is the lack of
>> availability of a feasible distribution for Symfony2.
>> Subtree merge only solves half of the problem, since you would still
>> need to download the entire repo.
> 
> I've written a tool that can be used to identify component-level
> dependencies for a given ZF component, which should make it fairly
> trivial to extract the components individually (especially since no
> classes live directly under the "Zend" namespace in ZF2). That work is
> here on GitHub:
> 
>    https://github.com/weierophinney/zf-examples/tree/master/zf-utils
> 
> (The bin/scanDeps.php script is the one to use; it has dependencies
> within that tree.)
> 
> Could that help solve the problem of what to merge in to the sf tree?
> That way you can update it when preparing for a release, and not need to
> have the entire ZF library as a submodule or subtree merge.
> 
> -- 
> Matthew Weier O'Phinney
> Project Lead            | [email protected]
> Zend Framework          | http://framework.zend.com/
> PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

Lukas Kahwe Smith
[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