basil commented on PR #210:
URL: https://github.com/apache/ant/pull/210#issuecomment-2322905284

   > And we do not want to have our fork to be the general purpose single 
source that others would depend on. Depending on Ant as a whole would be 
strange for people who only want to create tars.
   
   I think there is demand for a dependency-free general-purpose tar/untar 
implementation (as evidenced by the fact that I was not the only Commons 
Compress user to complain about the new dependency on Commons Lang 3), should 
the Ant maintainers choose to go in this direction (e.g. by accepting PRs like 
this). Depending on Ant as a whole was not strange for us, since we already use 
Ant for other functionality inside Jenkins.
   
   > No, we don't really change the code much. It's been serving Ant well for a 
long time and we only change things if bugs are reported.
   
   If you do need to change the code, though, it would be easier to port future 
bug fixes from Commons Compress if the two codebases were more similar. The 
more the two codebases diverge, the more challenging it becomes to port fixes 
from Commons Compress to Ant for the portions that are actually used by Ant.
   
   > The Apache Software License certainly allows forking the code. So one way 
for Jenkins could be to fork the tar package from Commons Compress and strip it 
off its dependencies. Of course you'd have to carry the burden of maintaining 
it, then.
   
   Indeed. I think we can all agree that maintaining forks is a maintenance 
burden that should be avoided if possible. This PR is an attempt to optimize 
globally rather than locally, trying to find an equilibrium between all three 
projects—should the Ant project judge the maintenance cost associated with this 
(unit-tested) PR to be acceptable.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Reply via email to