Hi!
I've just discovered the make option "make package-noinstall" which
makes a tbz in /usr/ports/packages from a already installed package.
But I've also found a bug(?) with that option. The package it creates
seems not to include rc.d script which will be included if you use
"make package"
I've
On Sat, Feb 20, 2010 at 04:55:58PM +0100, Christer Solskogen wrote:
> Hi!
>
> I've just discovered the make option "make package-noinstall" which
> makes a tbz in /usr/ports/packages from a already installed package.
> But I've also found a bug(?) with that option. The package it creates
> seems n
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
