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 sec
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
> >
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.
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
Pav Lucistnik wrote:
> Dominic Fandrey píše v so 28. 03. 2009 v 19:23 +0100:
>
>> I'm working on a binary package upgrade tool that gets all required
>> information from the INDEX file downloadable from the package
>> repositories. This means you do not need a local copy of the ports
>> tree to us
Dominic Fandrey píše v so 28. 03. 2009 v 19:23 +0100:
> I'm working on a binary package upgrade tool that gets all required
> information from the INDEX file downloadable from the package
> repositories. This means you do not need a local copy of the ports
> tree to use it.
>
> The only informati
