On Sat, 14 Oct 2006 23:54:08 -0500, Doug Barton <[EMAIL PROTECTED]> wrote:
John Hay wrote:
It looks like ports/UPDATING is mixing sysutils/portmanager and
portmaster in the 20061014 part that tells how to update gnome. Is
that on purpose?
The entry says this:
20061014:
AFFECTS: All
John Hay wrote:
It looks like ports/UPDATING is mixing sysutils/portmanager and
portmaster in the 20061014 part that tells how to update gnome. Is
that on purpose?
The entry says this:
20061014:
AFFECTS: All GNOME users
AUTHOR: [EMAIL PROTECTED]
GNOME has been updated to 2.16 and all
On Sat, 14 Oct 2006 23:00:27 -0500, Doug Barton <[EMAIL PROTECTED]> wrote:
For future reference, take a look at how I handle this in the BIND
ports. If you'd named the _port_ 0.3.a1_2, then when 0.3 comes out,
pkg_version is smart enough to know that it's > 0.3.a*.
It is too late, which in
On Sat, Oct 14, 2006 at 09:00:27PM -0700, Doug Barton wrote:
> For future reference, take a look at how I handle this in the BIND
> ports. If you'd named the _port_ 0.3.a1_2, then when 0.3 comes out,
> pkg_version is smart enough to know that it's > 0.3.a*.
>
> hth,
>
> Doug
>
> PS, PORTEPOCH
Matthew Seaman wrote:
Dear port maintainer,
MOVED says:
:devel/avr-gcc-devel|devel/avr-gcc|2006-10-06|make AVR-GCC 4.x the default
version
UPDATING says:
The former avr-gcc-devel port has been moved into avr-gcc, so GCC
4.x is now the default.
but there is still an entry in
For future reference, take a look at how I handle this in the BIND
ports. If you'd named the _port_ 0.3.a1_2, then when 0.3 comes out,
pkg_version is smart enough to know that it's > 0.3.a*.
hth,
Doug
PS, PORTEPOCH is evil, and must die.
Jeremy Messenger wrote:
Fixed by add PORTEPOCH, tha
>Submitter-Id: current-users
>Originator:Olli Hauer
>Organization:
>Confidential: no
>Synopsis: [patch] port mail/sqlgrey make with -DWITH_PGSQL
>Severity: non-critical
>Priority: low
>Category: ports
>Class: update
>Release: FreeBSD 6.1-RELEASE-p10 i386
>En
On Saturday 14 October 2006 21:14, John Hay wrote:
> It looks like ports/UPDATING is mixing sysutils/portmanager and
> portmaster in the 20061014 part that tells how to update gnome. Is
> that on purpose?
The instuctions are for portmaster; the mention of sysutils/portmanager looks
li
On 10/14/06, Michael Johnson <[EMAIL PROTECTED]> wrote:
On 10/14/06, John Hay <[EMAIL PROTECTED]> wrote:
>
> It looks like ports/UPDATING is mixing sysutils/portmanager and
> portmaster in the 20061014 part that tells how to update gnome. Is
> that on purpose?
>
it&#x
On 10/14/06, John Hay <[EMAIL PROTECTED]> wrote:
It looks like ports/UPDATING is mixing sysutils/portmanager and
portmaster in the 20061014 part that tells how to update gnome. Is
that on purpose?
it's not mixing, it's giving you the option to use portmaster OR portmanager
It looks like ports/UPDATING is mixing sysutils/portmanager and
portmaster in the 20061014 part that tells how to update gnome. Is
that on purpose?
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
Fixed by add PORTEPOCH, thanks for report.
Cheers,
Mezz
On Sat, 14 Oct 2006 12:54:09 -0500, <[EMAIL PROTECTED]> wrote:
** The following ports have a version number that sorts before a
previous one **
For many package tools to work correctly, it is of utmost importance
that
version numbe
By the way, if anyone have any problem with login in GNOME after the
upgrade such as slow or maybe get a very small error. Try to run this
gnome_prefix.sh[1] script as in your orignal user to fix the ~/.* files if
you don't want to remove your GNOME config. Let me know if it helps. If
the
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
Scott T. Hildreth writes:
> Is there an upgrade script or do we just do a portupgrade?
Check /usr/ports/UPDATING.
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On Sat, 2006-10-14 at 11:48 -0500, Scott T. Hildreth wrote:
> Is there an upgrade script or do we just do a portupgrade?
As with every major upgrade (GNOME or otherwise)
consult /usr/ports/UPDATING.
Joe
>
>
> On Sat, 2006-10-14 at 10:52 -0500, Scott T. Hildreth wrote:
>
> > Bravo, I know the
Nevermind, I'm sure the directions are the same as 2.14 listed
on the www.freebsd.org/Gnome
On Sat, 2006-10-14 at 11:48 -0500, Scott T. Hildreth wrote:
> Is there an upgrade script or do we just do a portupgrade?
>
>
> On Sat, 2006-10-14 at 10:52 -0500, Scott T. Hildreth wrote:
> > Bravo, I k
Is there an upgrade script or do we just do a portupgrade?
On Sat, 2006-10-14 at 10:52 -0500, Scott T. Hildreth wrote:
> Bravo, I know the team had to do a lot of work to get this in before
> 6.2,
> so great job everyone!
>
>
> On Sat, 2006-10-14 at 05:42 -0400, Joe Marcus Clarke wrote:
>
>
Dear port maintainer,
MOVED says:
:devel/avr-gcc-devel|devel/avr-gcc|2006-10-06|make AVR-GCC 4.x the default
version
UPDATING says:
The former avr-gcc-devel port has been moved into avr-gcc, so GCC
4.x is now the default.
but there is still an entry in devel/Makefile for avr-
Bravo, I know the team had to do a lot of work to get this in before
6.2,
so great job everyone!
On Sat, 2006-10-14 at 05:42 -0400, Joe Marcus Clarke wrote:
> The FreeBSD GNOME Team is proud to announce that GNOME 2.16.1 has been
> imported into the ports tree in time for FreeBSD 6.2. This is
Oops, I found a problem in print/freetype2. Please add missing #.
Index: Makefile
===
RCS file: /home/ncvs/ports/print/freetype2/Makefile,v
retrieving revision 1.75
diff -u -r1.75 Makefile
--- Makefile14 Oct 2006 08:35:43
Oops, I found a problem in print/freetype2.
Please add missing #.
Index: Makefile
===
RCS file: /home/ncvs/ports/print/freetype2/Makefile,v
retrieving revision 1.75
diff -u -r1.75 Makefile
--- Makefile14 Oct 2006 0
Τα καλύτερα gadget της αγοράς! Απίθανα και μοναδικά δώρα για φανατικούς
gadgetάκιδες!
Αν δεν μπορείτε να δείτε την εικόνα που ακολουθεί, κάντε κλικ
http://r.vresp.com/?HelleniceBusinessSol/e49b7e36eb/730848/810f79b556/9f11daf
για να την δείτε στον browser σας.
_
Cheng-Lung Sung wrote:
Hi,
I have submit ports/104325 for p5-forks. You can try it.
Regards,
On Wed, Oct 11, 2006 at 11:24:17PM +0200, Peter Ankerst嶚 wrote:
Hi all,
I'm trying to create a port for the first time and it is a perl-script...
I've created an Makefile and all the steps in
On Sat, 14 Oct 2006 05:42:41 -0400, Joe Marcus Clarke wrote:
> The FreeBSD GNOME Team is proud to announce that GNOME 2.16.1 has been
> imported into the ports tree in time for FreeBSD 6.2. This is a first.
> Usually the GNOME release cycle has conflicted with the FreeBSD release
> cycle. However
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the li
The FreeBSD GNOME Team is proud to announce that GNOME 2.16.1 has been
imported into the ports tree in time for FreeBSD 6.2. This is a first.
Usually the GNOME release cycle has conflicted with the FreeBSD release
cycle. However, thanks to Kris and pointyhat, we were able to get the
major patch t
On Sat, 14 Oct 2006 01:11:46 -0500
"Scot Hetzel" <[EMAIL PROTECTED]> wrote:
> On 10/13/06, lveax <[EMAIL PROTECTED]> wrote:
> > hey all,i can't fetch the distfile when i update pdflib,would
> > anyone fix it?
> >
> >
> Looks like the file is no longer on the web site. Instead there is a
> new ver
in message <[EMAIL PROTECTED]>,
wrote Dmitry Marakasov thusly...
>
> for port in `pkg_info -oaq`; do
> grep OPENSSL /usr/ports/$port/Makefile >/dev/null &&
> echo $port;
> done
>
> This will list all ports that use OPENSSL, and no need to search
> for executables/libs linked wi
29 matches
Mail list logo
