Fw: Upgrading Perl... yesterday's AWK improved, working...

[Jeffrey Bouquet]

Sorry for top-posting...  [ other email services are on my todo list (  hushmail, runbox, polarismail,  if/when the

email volume here increases... ]


the +MTREE_DIRS pipe can be extended...

....... | grep -v "v 2" [OMITTING Nov 21 already-updateds] | awk '{print $9}' | gtr -s \/ "\n" | grep p5 | xargs -J % portmaster -d -B -i -g % 

&& yell || yell

............................

If one has gnuls, gtr (coreutils?) installed, and still uses /var/db/pkg/PORTNAME-NUMBER, that pipe (the second part above, the
first below...)  just updated at-once 14 of the hundreds of p5 ports as I had updated the head -115 to head -135 ( approximately).

I expect to copy [1] that !hint to all /lang/ (perl ) (ruby) (python) to use until pkgng, at which point I hope that someone has posted

a PKG equivalent... or evolved a feature of PKG where it writes its /var/db/pkg files out again after each operation, so equivalent

pipes can occur. 


1.. actually, scrot of this email before sending, so more information included.  ( the .jpg to the /lang/ directories...) 






On Friday, November 22, 2013 4:17 AM, Jeffrey Bouquet <jeffreybouquet at yahoo.com> wrote:
 
I *was* equally setback by this upgrade, but am slowly mostly fixing it on a build machine to maybe package over to the usual one:

(My quicker pipes have not been working ...)

..................................

cd /var/db/pkg

gnuls -oSr | grep p5 | head [.... increment each time... 10, 20...] | awk '{print $8 }' xargs -J % find % -type f

-name +MTREE_DIRS  -exec /bin/ls -lac {} \; 

....................................

[ more to the pipe maybe automates the next ...]

.......................................

You'll see ports *since* last upgrading perl and *not since*.  Simply type the older ones into

portmaster -d -B -i -g p5-...... p5-........... p5-.....

.....................................

I am in a rush on some aspects of this update, so on ones which don't install

use something like...

cd /usr/ports/net/p5-Socket

/bin/rm -rf work

make -DNO_STAGE -DMAKE_JOBS_UNSAFE -DNO_PACKAGE reinstall

....................

YMMV.  [ It is quite obviously piecemeal, this method...]

..................

Another glitch with this upgrade, every Nth port seemingly wants to revert perl 5.16 > 5.14 in the process of

install from a package, so I've often

/bin/rm -v /usr/bin/perl

/bin/rm -v /usr/bin/perl5

/bin/rm -v /usr/local/bin/perl

ln -s /usr/local/bin/perl5.16.3 /usr/local/bin/perl

ln -s /usr/local/bin/perl5.16.3 /usr/bin/perl

ln -s /usr/local/bin/perl5.16.3 /usr/bin/perl5

After cntl-c the new failing install-older-perl package *BEFORE* it installs the older perl *ALSO*.... 

.............................

If I am wiser next time, and maybe even on this older-perl machine, I'll simply delete all p5-s after printing them out,

and awk / gtr /xargs the file into portmaster.   I expect the workarounds to still be maybe necc. though.

.............................



J. Bouquet 

Sorry for typos 




On Friday, November 22, 2013 3:52 AM, Mathieu Arnold <mat at mat.cc> wrote:

+--On 22 novembre 2013 00:25:26 -0800 "Ronald F. Guilmette"
<rfg at tristatelogic.com> wrote:
|   AUTHOR: mat at FreeBSD.org

Cough, cough, yeah, I mostly wrote that.

|         portupgrade -o lang/perl5.16 -f perl-5.14.\*

At that time, that line was right. Now, after that, the perl packages name
which had the same name (all named perl) and were conflicting and were
renamed to perl5 for the default perl, that is, 5.16, and perl5.xx for the
non default ones, that are 5.12, 5.14 and 5.18.

| pkg_info says that at present I have perl5.14-5.14.4_3 installed.  So
| excuse my french, but why the fuck didn't the command:
| 
|    portupgrade -o lang/perl5.16 -f perl-5.14.\*

Now, as you can see, your perl is not named perl-5.14 but
perl5.14-5.14.4_3, so, you should change that line to :
portupgrade -o lang/perl5.16 -f perl5.14-5.14.4_3

I'll commit an update to that right now.

-- 
Mathieu Arnold
_______________________________________________
freebsd-ports at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"

_______________________________________________
freebsd-ports at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"