Hi Chris, On 3/24/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > As I've said, my only request is a single policy that before an overlay > can become publicly readable on overlays.gentoo.org (which is Gentoo > infrastructure) that it does not break packages in the main tree that > are not in the overlay. > > If this single policy were in place, then I would fully support > overlays.gentoo.org being created.
I accept the principle. I've just one question about the practice. Overlays will (probably more often than not) contain packages that have problems. For example, I'm thinking of when we developed the new PHP packages, the packages delivered PHP in a new way, with different USE flags. We deliberately added a blocker, so that dev-lang/php and dev-php/php (the version from the tree) couldn't be installed at the same time. This meant that, until the webapps had their DEPs updated, if you had PHP from the overlay installed, it would block webapps from the tree from installing (because they depended on dev-php/php). Do you consider a practice like that to violate the policy you seek? Best regards, Stu -- gentoo-dev@gentoo.org mailing list
