On Sunday 16 January 2011 21:27:26 Marc Espie wrote: > I now have two normally bright guys asking weird questions about it works. > > EPOCH is stupid, it's awfully simple. > > A port that gets EPOCH means the version numbering got fucked up. > > So it starts anew. > > From scratch ! > > if you set EPOCH=0, that will append a v0 to the pkgname. > > ANYTHING with v0 is more recent than ANYTHING without, always. That's just > some new numbering, you start anew, pkgtools won't peek, they won't care, > it's just newer. > > so, e.g., > > $ pkg_info -r py-qt4-1.0v0 'py-qt4->=4.8' > Pkgspec py-qt4-1.0v0 matched > > (and if you fuck up again, you go to v1, then v2...) > > That's totally simple. If you can avoid it, you don't want EPOCH. > > But you can't predict the future. So if you fuck up your numbers, EPOCH is > for you. > > > Don't hesitate to experiment with -current pkg_info -r until you get it !
Hi, I read about this variable just now. You described well how to use it, but I am curious, how or when does it go away from the Makefile if v0 is newer than anything else? -- Antti Harri
