I agree with this and it's a very good idea IMO but the problem is that sometimes people just really want to or need to work on that package in mainline even though it's being worked on in a WIP also. We need to address this problem somehow.
On Tue, Mar 11, 2014 at 4:00 PM, kikadf <[email protected]> wrote: > Hi! > > I notice that we have some problem with the WIP repos, sometimes cause > plus work for the WIP repo owner a package bump in current what is part the > affected WIP repo. > > I think we should freeze the package bumps, what is part a WIP repo : > > 1. In every WIP repo add a freeze.txt in source dir, what is similar the > searchabi output. Just similar, because the searchabi not show if the > affected package just a subpackage. Need the mother package. > > 2. Add a hook for git, what is check the freeze.txt of WIP repos. If the > sent patch modify a package in current what is in freeze.txt files, reject > the patch and give a short log: this package freeze in $foo WIP repo, > contact the owner. > > 3. After the WIP repo merging to current, should remove the freeze.txt. > > > > (Maybe we can generate a "industry" page in homepage, what is list the > actually used WIP repo, what build, and a link the WIP repo's freeze.txt. > Maybe add an search box, when we can search a package, is it freezing? > > For example: > > dex77testing :gcrypt, gnutls, tasn1 bump link to freeze.txt > mcirstabumps :bump everything link to freeze.txt > > |_______________|_ Search_| Search package in freeze lists.) > > > > > > > _______________________________________________ > Frugalware-devel mailing list > [email protected] > http://frugalware.org/mailman/listinfo/frugalware-devel >
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
