Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
On Wed, Mar 6, 2013 at 9:00 PM, Chris Rees utis...@gmail.com wrote: Portdowngrade now simply checks out the port to your current directory; if you run it in ~, you simply cd $portname. I got bitten by this change today. I think portdowngrade should warn users that it will work on the current directory, not the port directory. Something like: NOTE: this program will check out the new port into a directory named $portname in your current directory. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
OK, done :) Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Hey, I rewrote it in sh, quite simply because I thought that c++ was insane for such simple code. I'm afraid it doesn't quite have the same behaviour, but it's still very easy to use. Please let me know if there's something you desperately miss about the old version. Chris Thanks for your effort! # portdowngrade audio/oss Listed all revisions # portdowngrade audio/oss r300895 I've picked one from the past However: # portsnap fetch update Is blind to this change and fails to update it back, to it's latest version portdowngrade should also alter/update portsnap's DB Domagoj Smolčić ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
On Wed, Mar 6, 2013 at 11:15 AM, rank1see...@gmail.com wrote: http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Hey, I rewrote it in sh, quite simply because I thought that c++ was insane for such simple code. I'm afraid it doesn't quite have the same behaviour, but it's still very easy to use. Please let me know if there's something you desperately miss about the old version. Chris Thanks for your effort! # portdowngrade audio/oss Listed all revisions # portdowngrade audio/oss r300895 I've picked one from the past However: # portsnap fetch update Is blind to this change and fails to update it back, to it's latest version portdowngrade should also alter/update portsnap's DB Domagoj Smolčić Portdowngrade always warned that portsnap would always overwrite any altering of the origin, which I believe is still the best path. If anything a warning should be displayed, if not already. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
On 6 Mar 2013 19:15, rank1see...@gmail.com wrote: http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Hey, I rewrote it in sh, quite simply because I thought that c++ was insane for such simple code. I'm afraid it doesn't quite have the same behaviour, but it's still very easy to use. Please let me know if there's something you desperately miss about the old version. Chris Thanks for your effort! # portdowngrade audio/oss Listed all revisions # portdowngrade audio/oss r300895 I've picked one from the past However: # portsnap fetch update Is blind to this change and fails to update it back, to it's latest version portdowngrade should also alter/update portsnap's DB Portdowngrade now simply checks out the port to your current directory; if you run it in ~, you simply cd $portname. I wouldn't recommend the old behaviour of downgrading in place like that; it significantly complicates many things, including svn conflicts and portsnap update maybe overwriting it, maybe not. I view it as a tool for testing older versions/reverting until a fix is issued. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
Doesn't the old advice of adding, something like REFUSE audio/oss to /etc/portsnap.conf still work? - Original Message - On Wed, Mar 6, 2013 at 11:15 AM, rank1see...@gmail.com wrote: http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Hey, I rewrote it in sh, quite simply because I thought that c++ was insane for such simple code. I'm afraid it doesn't quite have the same behaviour, but it's still very easy to use. Please let me know if there's something you desperately miss about the old version. Chris Thanks for your effort! # portdowngrade audio/oss Listed all revisions # portdowngrade audio/oss r300895 I've picked one from the past However: # portsnap fetch update Is blind to this change and fails to update it back, to it's latest version portdowngrade should also alter/update portsnap's DB Domagoj Smolčić Portdowngrade always warned that portsnap would always overwrite any altering of the origin, which I believe is still the best path. If anything a warning should be displayed, if not already. -jgh -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
On 6 March 2013 21:32, Lawrence K. Chen, P.Eng. lkc...@ksu.edu wrote: Doesn't the old advice of adding, something like REFUSE audio/oss to /etc/portsnap.conf still work? I hope I haven't upset anyone with the change in behaviour, but I need to reiterate that portdowngrade no longer touches the ports tree-- it simply provides a port skeleton in the current directory. Therefore, this is no longer a problem. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
- Original Message - On 6 March 2013 21:32, Lawrence K. Chen, P.Eng. lkc...@ksu.edu wrote: Doesn't the old advice of adding, something like REFUSE audio/oss to /etc/portsnap.conf still work? I hope I haven't upset anyone with the change in behaviour, but I need to reiterate that portdowngrade no longer touches the ports tree-- it simply provides a port skeleton in the current directory. Therefore, this is no longer a problem. Chris Except I don't know of another way to downgrade a port to work with other portsperhaps there's a way in portmaster.rc that I haven't stumbled upon yet. I know I had something in pkgtools.conf at one time to prevent virtualbox from upgrading (has istgt been updated to work with the current virtualbox yet? Have since removed istgt) Forget what the other time that I used portdowngradesomething to do with X11 I think, which was resolved by rebuilding with WITH_NEW_XORG=YES in my /etc/make.conf. OTOH, there are parts of my ports tree that I have to remember to 'update' after a 'portsnap update'like www/chromium Lawrence ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
On 4 January 2013 19:59, rank1see...@gmail.com wrote: http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Hey, I rewrote it in sh, quite simply because I thought that c++ was insane for such simple code. I'm afraid it doesn't quite have the same behaviour, but it's still very easy to use. Please let me know if there's something you desperately miss about the old version. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portdowngrade(CVS) deprecated - alternative for portsnap(8) usage
http://forums.freebsd.org/showthread.php?p=203241 Will it be transformed to checkout via SVN, only origins we need, or will it be dumped from ports tree as obsolete. Thanks. Domagoj ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
