Landry Breuil <lan...@rhaalovely.net> wrote:

> On Wed, Jan 13, 2010 at 10:27:38AM -0600, nealHogan wrote:
> > On Wed, Jan 13, 2010 at 04:05:04PM +0000, Owain Ainsworth wrote:
> > > On Tue, Jan 12, 2010 at 09:02:47PM -0600, Abel Abraham Camarillo Ojeda 
> > > wrote:
> > > > Port attached.
> > > 
> > > And it can't fetch the distfile:
> > > 
> > > o...@leah/p9:/usr/ports/mystuff/www/vimprobable$ make package
> > > ===>  Checking files for vimprobable-20100105p0
> > > >> Fetch
> > > http://ftp.lambdaserver.com/pub/viStuff/vimprobable-20100105.tar.gz
> > > ftp: Error retrieving file: 404 Not Found
> > > >> Fetch
> > > ftp://ftp.openbsd.org/pub/OpenBSD/distfiles//vimprobable-20100105.tar.gz
> > > vimprobable-20100105.tar.gz: No such file or directory.
> > > 
> > >
> > 
> > It should work now. 
> > 
> > FYI - the file that was on my site was vimprobable-20100105p0.tar.gz. 
> > I didn't expect the new version to fetch a file with the old name (i.e., 
> > minus  'p0'). Anyway, the same file is there under both names.
>
> Err... that is deeply dumb. p0 is here for PKGNAME, if you smack it into
> DISTNAME you're going to face issues. roll it as 20100113.tar.gz or
> whatever, but not xxxxp0.tar.gz. If you try to fetch the old distfile
> (which changed), checksum wont' match.
> Sometimes i wonder if ppl read bsd.port.mk(5), package-specs(7) and the
> faq/ports pages...
>
> Landry

There is the confusion here:

The distfile didn't changed (the "upstream" source code is the same), the 
package
indeed changed because you can only add options to :open in compile time
changing the config.h (peerboom?) so the binary PREFIX/bin/vimprobable2 was
different, and also the PLIST changed because of the comments from landry, so i 
added a p0 so the guys who tested the previous version can test this without
problems...

But it seems that Neal has been playing a lot with the distfiles (he is hosting
it)...

Neal: you don't need to change anything.

Sorry for all this mess...

--
DISCLAIMER: http://goldmark.org/jeff/stupid-disclaimers/ 
This message will self-destruct in 3 seconds.

Reply via email to