Brokenness caused by libpng update

Riccardo Mottola rmottola at opencsw.org
Thu May 7 20:36:51 CEST 2015


Hi,

On 05/06/15 10:00, Laurent Blume wrote:
> I was not blaming you. You have to understand that when you're working
> with packages that impact the work of other people, you fully assume the
> responsibility of not disturbing the work of those people more than
> necessary, and fix new issues that appear.

no offense taken! It is just that I happened to awaken a problem about 
versioning here.

> This is tangent to Peter's recent post. We get the feeling that for you,
> this is a hobby, you play and learn on obsolete OS's. That's a perfectly
> fine and legit reason to work with OpenCSW.
> But others still have actual business needs for those packages you are
> impacting with your changes. You are very welcome to make those changes,
> but you do have to be careful and responsible with them.

True, my work doesn't depend on these OpenCSW packages. However I strive 
for quality. I am an "upstream developer" and I like to take care about 
the software I like on solaris/sparc and generally I want to make life 
easier for other users, both professional and hobbyists, by providing 
up-to-date packages

I didn't expect that an update would cause such a problem, but now that 
there is a path to the solution.

I hope that after this upgade it will be etter for anybody: the 
versioning is the solution you proposed. Just making it work has some 
itches.


>
> Yes, that is precisely why I said you have to contact the maintainers 
> of the dependencies of your package to make sure that they are aware 
> of those changes they have to make. Welcome to dependency hell. It's 
> part of the job :-)

I hope the current build will provide the necessary packages and that 
they will work. I'll leave the wiki page open for all packages to be 
updated sooner or later!

Riccardo



More information about the maintainers mailing list