Early CONFLICTS detection is POLA viloation?
in [Ports]
|
Prev: Port variables to respect (was Re: mail/thunderbird3 does not buildwith gcc 4.5.1)
Next: ports/148192: version update
From: Lev Serebryakov on 27 Jun 2010 14:04 Hello, Freebsd-ports. I understand, that this change (ports/137855, bsd.port.mk:1.632) was made 6 months ago, but I've noticed it only now (twice in one day!). Am I only person, who thinks, that this change is HUGE POLA violation? PR says about "big tarball is downloaded and CONFLICTS are detected after that," but I've have two more realistic scenarios, when early conflict detection is VERY annoying. Thry are real-life scenarios, occured today for me in a row. (1) I have `subversion' port installed, and want to `makesum' in updated subversion-freebsd port directory (because I'm maintainer and need to update port with new version, which have new tarball). OOPS. I cannot even download new tarball -- confilct is detected. (2) I want upgrade perl from 5.8.x to 5.10.x. Type command: #portupgrade -rfo lang/petl5.10 perl-5.8.9_3 Ooops, confilct is detected, upgraid failed. GRRRR! Maybe, early conflict detection should only print WARNING, and only install target should be blocked by it, as everybody used for MANY years? -- // Black Lion AKA Lev Serebryakov <lev(a)FreeBSD.org> _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Garrett Cooper on 27 Jun 2010 14:24 2010/6/27 Lev Serebryakov <lev(a)freebsd.org>: > Hello, Freebsd-ports. > > I understand, that this change (ports/137855, bsd.port.mk:1.632) was made 6 months ago, but I've > noticed it only now (twice in one day!). > > Am I only person, who thinks, that this change is HUGE POLA > violation? > > PR says about "big tarball is downloaded and CONFLICTS are detected > after that," but I've have two more realistic scenarios, when early > conflict detection is VERY annoying. Thry are real-life scenarios, > occured today for me in a row. > > (1) I have `subversion' port installed, and want to `makesum' in > updated subversion-freebsd port directory (because I'm maintainer and > need to update port with new version, which have new tarball). OOPS.. > I cannot even download new tarball -- confilct is detected. > > (2) I want upgrade perl from 5.8.x to 5.10.x. Type command: > > #portupgrade -rfo lang/petl5.10 perl-5.8.9_3 > > Ooops, confilct is detected, upgraid failed. GRRRR! > > > Maybe, early conflict detection should only print WARNING, and only > install target should be blocked by it, as everybody used for MANY > years? I'm in a similar boat as you when I was trying to eval some of the linux base / dist ports recently. I would think that the CONFLICTS detection should only be a warning in the first run-through, and become a hard error when you try and run make install. Thanks, -Garrett _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Steven Hartland" on 27 Jun 2010 14:40 Had the same here when trying to upgrade things, I don't want to have to uninstall the current version before I can build the new one only to find out there is some issue and have to roll back. I've ended up commenting out the conflicts and ignoring them, which I'm sure is not the desired behaviour :( Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster(a)multiplay.co.uk. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Philip M. Gollucci" on 27 Jun 2010 15:22 make -DDISABLE_CONFLICTS On 6/27/2010 2:04 PM, Lev Serebryakov wrote: > Hello, Freebsd-ports. > > I understand, that this change (ports/137855, bsd.port.mk:1.632) was made 6 months ago, but I've > noticed it only now (twice in one day!). > > Am I only person, who thinks, that this change is HUGE POLA > violation? > > PR says about "big tarball is downloaded and CONFLICTS are detected > after that," but I've have two more realistic scenarios, when early > conflict detection is VERY annoying. Thry are real-life scenarios, > occured today for me in a row. > > (1) I have `subversion' port installed, and want to `makesum' in > updated subversion-freebsd port directory (because I'm maintainer and > need to update port with new version, which have new tarball). OOPS. > I cannot even download new tarball -- confilct is detected. > > (2) I want upgrade perl from 5.8.x to 5.10.x. Type command: > > #portupgrade -rfo lang/petl5.10 perl-5.8.9_3 > > Ooops, confilct is detected, upgraid failed. GRRRR! > > > Maybe, early conflict detection should only print WARNING, and only > install target should be blocked by it, as everybody used for MANY > years? > -- ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci(a)p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer, FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching.
From: Warren Block on 27 Jun 2010 15:43
On Sun, 27 Jun 2010, Lev Serebryakov wrote: > Hello, Freebsd-ports. > > I understand, that this change (ports/137855, bsd.port.mk:1.632) was made 6 months ago, but I've > noticed it only now (twice in one day!). > > Am I only person, who thinks, that this change is HUGE POLA > violation? > > PR says about "big tarball is downloaded and CONFLICTS are detected > after that," but I've have two more realistic scenarios, when early > conflict detection is VERY annoying. Thry are real-life scenarios, > occured today for me in a row. > > (1) I have `subversion' port installed, and want to `makesum' in > updated subversion-freebsd port directory (because I'm maintainer and > need to update port with new version, which have new tarball). OOPS. > I cannot even download new tarball -- confilct is detected. > > (2) I want upgrade perl from 5.8.x to 5.10.x. Type command: > > #portupgrade -rfo lang/petl5.10 perl-5.8.9_3 > > Ooops, confilct is detected, upgraid failed. GRRRR! > > > Maybe, early conflict detection should only print WARNING, and only > install target should be blocked by it, as everybody used for MANY > years? It's been mentioned before: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137855 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |