In article <[EMAIL PROTECTED]>,
Alexander Leidinger <[EMAIL PROTECTED]> wrote:
> On 10 Jul, Will Andrews wrote:
>
> >> Only if ports-base isn't anymore in ports-all or my local CVS tree is
> >
> > ports-base was/has never [been] in ports-all, for some strange reason.
>
> Really?
[...]
> I read
On 10 Jul, Will Andrews wrote:
>> Only if ports-base isn't anymore in ports-all or my local CVS tree is
>
> ports-base was/has never [been] in ports-all, for some strange reason.
Really?
/usr/share/examples/cvsup/ports-supfile:
---snip---
## Ports Collection.
#
# The easiest way to get the por
On Mon, 10 Jul 2000 11:44:08 EST, Ade Lovett wrote:
> On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote:
> > But you didn't update /usr/ports/Mk, did you? :-)
>
> This is nothing to do with parts of /usr/ports being out of date
> and has already been mentioned on both -ports and -c
On Mon, Jul 10, 2000 at 07:15:31PM +0200, Alexander Leidinger wrote:
> Only if ports-base isn't anymore in ports-all or my local CVS tree is
ports-base was/has never [been] in ports-all, for some strange reason.
--
Will Andrews <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+
On 10 Jul, Ade Lovett wrote:
>> But you didn't update /usr/ports/Mk, did you? :-)
Only if ports-base isn't anymore in ports-all or my local CVS tree is
messed up.
But you didn't do an »grep -i pod /usr/ports/Mk/*«, did you? :-)
> This is nothing to do with parts of /usr/ports being out of date
> On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote:
> > But you didn't update /usr/ports/Mk, did you? :-)
>
> This is nothing to do with parts of /usr/ports being out of date
> and has already been mentioned on both -ports and -current.
Will fix now...
M
--
Mark Murray
Join the ant
On Mon, Jul 10, 2000 at 06:32:22PM +0200, Sheldon Hearn wrote:
> But you didn't update /usr/ports/Mk, did you? :-)
This is nothing to do with parts of /usr/ports being out of date
and has already been mentioned on both -ports and -current.
>From my -current box, which is most definitely up to da
On Mon, 10 Jul 2000 17:51:46 +0200, Alexander Leidinger wrote:
> after the messages about the perl update have settled I decided to
> update my perl-ports (p5-*), but I get a warning (the "echo $(PATH)"
> below is inserted into the port Makefile by me).
But you didn't update /usr/ports/Mk, did
Hi,
after the messages about the perl update have settled I decided to
update my perl-ports (p5-*), but I get a warning (the "echo $(PATH)"
below is inserted into the port Makefile by me).
---snip---
{0} [Magelan:/usr/ports/lang/p5-F77]
(28) root@ttyp1# make configure
===> Extracting for p5-ExtU
