Aiza writes:
> Where can I find the description of the /usr/ports/INDEX-8 file?
Try bsd.ports.mk.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-quest
Where can I find the description of the /usr/ports/INDEX-8 file?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
On Fri, 23 Jul 2010 16:56:56 +0800
Fbsd8 wrote:
> tree is no big deal, but I bet they don't do backups.
If that's an issue, don't back it up.
> That ports tree
> directory is a large resource hog if you lift the blinders and look
> at the big picture.
> Just my 2 cents.
Funnily enough that'
On 07/23/2010 01:56 AM, Fbsd8 wrote:
> Now about my project. Since about 4.0 I stopped using the ports tree
> method. I now all most totally use the package system. I do not upgrade
> a RELEASE but instead use the "install from scratch" method about a few
> weeks after a new RELEASE is published. S
On 07/23/2010 03:56 AM, Fbsd8 wrote:
> Now the Freebsd method of the 22,000 individual ports each with 3 to 5
> files is a method which has out lived its usefulness. TAKE NOTE: NO
> FLAME WAR INTENDED. I just think a option should exist for us who don't
> follow the bleeding edge. Sure to some peop
On 7/23/10, Fbsd8 wrote:
> b. f. wrote:
>>> Benjamin Lee wrote:
On 07/22/2010 06:20 PM, Fbsd8 wrote:
...
>>
> Well first thanks for the info you provided though it was all negative.
I think that you were misinterpreting what I wrote if you think that
it was all negative.
> I will explain wh
lem is in both cases the above ports require an existing INDEX file
to process and since I have none they don't work.
How can I just download the ports INDEX file?
Portsnap is not a solution.
I see in the source of porteasy that its fetching
http://www.freebsd.org/ports/INDEX-8.bz2
How can
e the ports tree with only the ports I use.
>>>
>>> Problem is in both cases the above ports require an existing INDEX file
>>> to process and since I have none they don't work.
>>>
>>> How can I just download the ports INDEX file?
>>> Port
le and which ever of the
category Makefiles you use (ie. the Makefiles one level down the tree).
Problem is in both cases the above ports require an existing INDEX file
to process and since I have none they don't work.
How can I just download the ports INDEX file?
Portsnap is not a solution.
You
efiles you use (ie. the Makefiles one level down the tree).
> Problem is in both cases the above ports require an existing INDEX file
> to process and since I have none they don't work.
>
> How can I just download the ports INDEX file?
> Portsnap is not a solution.
You can use
both cases the above ports require an existing INDEX file
to process and since I have none they don't work.
How can I just download the ports INDEX file?
Portsnap is not a solution.
Well, The INDEX file is a component of the ports tree distribution. If
you choose not to use the supported met
in both cases the above ports require an existing INDEX file
> to process and since I have none they don't work.
>
> How can I just download the ports INDEX file?
> Portsnap is not a solution.
Well, The INDEX file is a component of the ports tree distribution. If
you choos
ases the above ports require an existing INDEX file
to process and since I have none they don't work.
How can I just download the ports INDEX file?
Portsnap is not a solution.
___
You can use 'csup' to get the ports tree down. Y
both cases the above ports require an existing INDEX file
> to process and since I have none they don't work.
>
> How can I just download the ports INDEX file?
> Portsnap is not a solution.
> ___
> freebsd-questions@freebsd.org mai
process and since I have none they don't work.
How can I just download the ports INDEX file?
Portsnap is not a solution.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe,
15 matches
Mail list logo
