On Thursday, January 6, 2011, Maciej (Matchek) Blizinski <[email protected]> wrote:
>> > This works as long as you know in advance what the problem is. In > practice you often don't. For example, I would have never guessed > that there would be a problem around files vs symlinks in /opt/csw/lib > (in the mysql libraries thread[1]). I would have only hit it when > trying to submit my package. Thanks to the ITP thread I was able to > know about the issue in advance. > > You can say that it's a general issue with shared libraries, but we > wouldn't come across it if we didn't consider the specific case of a > package compiled in a custom prefix. certainly for bigger packages it is useful to mention it and ask for any gotchas. I shouldn't say "never announce". I also wanted to avoid giving maintainers the impression that from now on they "have to announce". that might discourage people from experimenting with a new package, if they aren't initially sure they want to take it on. _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
