Pav Lucistnik wrote: > Dominic Fandrey píše v pá 03. 04. 2009 v 11:46 +0200: >> Pav Lucistnik wrote: >>> Dominic Fandrey píše v st 01. 04. 2009 v 00:12 +0200: >>> >>>>> Upgrades are easy. Look up @comment ORIGIN line in +CONTENTS file of the >>>>> port being upgraded, then look up this value in second column of INDEX >>>>> file. >>>>> >>>> I don't see how this is connected to my question. >>>> >>>> I want people to be able to use LATEST_LINK to identify ports, >>>> e.g. apache for www/apache13, apache20 form www/apache20 and so >>>> forth. LATEST_LINK is a unique identifier, unfortunately >>>> neither recorded in the INDEX nor +CONTENTS. >>>> Also, to read it from +CONTENTS (if it were there) I'd have to >>>> know, which package is actually meant, which I don't know, >>>> because this is the information I want to find out. >>> Maybe you really want people to specify ports by ORIGIN, not by >>> LATEST_LINK ... >>> >> Actually I want people to be able to do both. Since this is a >> binary package only tool, I want people to be able to use the >> same parameters as they'd be able to use with "pkg_add -r". >> >> I have implemented some guessing by now and it fails very rarely. >> But it's not the kind of solution I like. > > You could ls -l Latest/ directory on the ftp server and parse the > output, but it's a huge hack.. >
That's actually trivial with netcat, I'm alread checking age and size of the index file on the server to find out weather I need to download a new copy. But the trouble is that I have to download the package so that I can get the origin from the +CONTENTS file. Internally the origin is used as the package identifier to access the index file. So I'd have to wait for the download before I could do any dependency checking. Possible, but it feels clumsy. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
