Marco Gaiarin wrote: > For sake of portability i setup my windows networks on different > branches of my organization in similar manner, so i can simply copy my > 'wpkg recipes' around servers. I just setup a DNS entry, so that "branchdc" or "\\branchdc" points to a nearest file server. Then, just use \\branchdc\software\firefox\... etc. paths for all windows networks, and the files are 100% portable. > But with portable system that walk about different branches, can be > easy that can be 'upgraded' by eveery branch. > For now i've solved this simply using the same packages, and moving > revision number accordingly. I don't think I understood what you mean here. > But could be that wpkg use some sort of 'server signature', so it stops > if found that the 'wpkg server' signature does not match client > signature? Here as well - I'm not sure what you mean. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |