Portupgrade a strom portu

[Miroslav Prýmek]

On 8.11.2009, at 23:46, Miroslav Prýmek wrote:

>
>> - build stroj na kterem se prekladaji a vyrabeji balicky s  
>> anonymnim FTP
>> s vypublikovanym /usr/ports
>> - v /usr/ports je potreba dodelat linky pub=>. FreeBSD=>. ports=>.
>> (i386|amd64)=>. - podle platformy build stroje, klienti musi byt  
>> stejny
>> packages-8.0-release=>packages packages-8-stable=>packages
>> - na klientskem stroji musi existovat /usr/ports, pouzivam portsnap a
>> omezeni adresaru, ktere se aktualizuji v /etc/portsnap.conf (zabira
>> do 100 MB ve /var/db/portsnap a do 600M v /usr/ports)
>> - env PACKAGEROOT=ftp://build.moje.dns pkg_add -r portupgrade
>> - env PACKAGEROOT=ftp://build.moje.dns portupgrade -PP <balicek>
>
> Tohle je VYBORNEJ tip! Diky. Tim bych se mohl uplne zbavit NFS, coz
> by mi docela zjednodusilo zivot. Vubec jsem si neuvedomil, ze takhle  
> to jde
> taky! ...a zaroven mam jistotu, ze  omylem nenainstaluju nic, co by  
> nebylo
> z me vlastni "repository" - super!
>
> jeste jednou dik :)

Tak jasani bylo asi trochu predcasny. Je tam jeden drobnej zadrhel -  
pokud neni
k dispozici balicek v potrebne verzi, tak natvrdo stahne ten, ktery je  
v Latest,
coz se mi moc nelibi. Jde to nejak zakazat? V manu portupgrade o tom  
nic nevidim :(

Test:
1. v $PORTSDIR/shells/bash/Makefile jsem o jednicku zvysil revizi
2. # portupgrade -vNPP bash

--->  Fetching bash-4.0.34_2
++ Will try the following sites in the order named:
	ftp://MUJSERVER/pub/FreeBSD/ports/i386/packages-7.2-release/

[ ... ... ]

** Failed to fetch bash-4.0.34_2
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
	! bash-4.0.34_2	(fetch error)
--->  Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
--->  Fetching the latest package(s) for 'bash' (shells/bash)
--->  Fetching bash
++ Will try the following sites in the order named:
	ftp://MUJSERVER/pub/FreeBSD/ports/i386/packages-7.2-release/
--->  Invoking a command: /usr/bin/fetch -o '/var/tmp/ 
portupgradeQ2RuGbko/bash.tbz' 'ftp://MUJSERVER/pub/FreeBSD/ports/i386/ 
packages-7.2-release/Latest/bash.tbz'
/var/tmp/portupgradeQ2RuGbko/bash.tbz         100% of  863 kB   53  
kBps 00m00s
--->  Downloaded as bash.tbz
--->  Identifying the package /var/tmp/portupgradeQ2RuGbko/bash.tbz
--->  Saved as /usr/ports/packages/All/bash-4.0.33_2.tbz
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
	+ bash@
--->  Packages processed: 1 done, 0 ignored, 0 skipped and 0 failed
--->  Found a package of 'shells/bash': /usr/ports/packages/All/ 
bash-4.0.33_2.tbz (bash-4.0.33_2)
--->  Located a package version 4.0.33_2 (/usr/ports/packages/All/ 
bash-4.0.33_2.tbz)
--->  Using it anyway although it is not the latest version  
(4.0.34_2), since -PP/--use-packages-only is specified
--->  Installing 'bash-4.0.33_2' from a package

Co s tim? Ignorovat to a davat si pozor na to, aby vzdycky vsechny  
balicky byly pred upgradem k dispozici
v posledni verzi? Nebo jednoduse po buildu obsah Latest smazat?

diky za komentare

Mirek