On 09/04/2012 10:45 AM, Scott Howard wrote: > On Tue, Sep 4, 2012 at 10:21 AM, Michael Hall <[email protected]> wrote: >> >> On 09/04/2012 09:39 AM, Scott Kitterman wrote: >>> The problem isn't just with file conflicts with current packages, it's that >>> these packages will now start using up distro namespace. If some app >>> developer package ships the file /usr/games/bird-game, even though there's >>> no >>> current conflict, there is a package sync'ed from Debian that also ships >>> /usr/games/bird-game then there's a conflict we have to resolve. In /opt >>> in a >>> proper vendor namespace this can never happen. >> >> If bird-game already exists in Extras, and then a different package is >> allowed into backports that will install files into the same location, >> then yes there is a possibility for a conflict. But I assume part of >> the backports approval process already checks for conflicts, as they may >> exist with another package in the stable release already, so that >> process could easily be extended to include Extras packages as well. > > I think people are more concerned with auto-import from Debian than > backports. Debian's approval process knows nothing about Extras, so > there is no mechanism or approval process that checks for conflicts. > Since Extras package won't be in the development release until FeatureFreeze, we can check them against the new packages imported from Debian before we forward-copy them from the previous stable release.
Michael Hall [email protected] -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
