FreeBSD unmaintained ports which are currently marked broken

2013-04-07 Thread linimon 
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 problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 7.x/8.x/9.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   biology/dotter
broken because: checksum mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=dotter


portname:   chinese/big5con
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con


portname:   chinese/bitchx
broken because: patch reject
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=bitchx


portname:   chinese/hztty
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty


portname:   databases/msql
broken because: Broken on FreeBSD 9+
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql


portname:   deskutils/libopensync-plugin-python-devel
broken because: fails to build with recent libopensync
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=libopensync-plugin-python-devel


portname:   deskutils/msynctool-devel
broken because: fails to build with recent libopensync
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=msynctool-devel


portname:   deskutils/simpleagenda
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=simpleagenda


portname:   devel/arm-rtems-binutils
broken because: many issues; see
https://www.rtems.org/bugzilla/show_bug.cgi?id=2099
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=arm-rtems-binutils


portname:   devel/arm-rtems-gcc
broken because: many issues; see
https://www.rtems.org/bugzilla/show_bug.cgi?id=2099
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=arm-rtems-gcc


portname:   devel/arm-rtems-gdb
broken because: many issues; see
https://www.rtems.org/bugzilla/show_bug.cgi?id=2099
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=arm-rtems-gdb


portname:   devel/dsss
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=dsss


portname:   devel/i386-rtems-binutils
broken because: many issues; see
https://www.rtems.org/bugzilla/show_bug.cgi?id=2099
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=i386-rtems-binutils


portname:   devel/i386-rtems-gcc
broken because: many issues; see
https://www.rtems.org/bugzilla/show_bug.cgi?id=2099
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=i386-rtems-gcc


portname:   devel/i386-rtem

FreeBSD ports which are currently marked broken

2013-04-07 Thread linimon 
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 problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 7.x/8.x/9.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   accessibility/yasr
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=yasr


portname:   audio/gdam
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gdam


portname:   audio/hydrogen
broken because: does not install
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=hydrogen


portname:   benchmarks/polygraph31
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31


portname:   biology/dotter
broken because: checksum mismatch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=dotter


portname:   cad/meshlab
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=meshlab


portname:   chinese/big5con
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con


portname:   chinese/bitchx
broken because: patch reject
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=bitchx


portname:   chinese/cxterm
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=cxterm


portname:   chinese/hztty
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty


portname:   comms/hso-kmod
broken because: does not build with USB2, please try comms/uhso-kmod
instead
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hso-kmod


portname:   comms/ib-kmod
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ib-kmod


portname:   comms/uticom
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=uticom


portname:   converters/pdf2djvu
broken because: does not build
build errors:
http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/pdf2djvu-0.5.11_10.log
 (Mar 14 00:22:50 UTC 2013)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=converters&portname=pdf2djvu


portname:   databases/drizzle
broken because: fails to build
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20130404090506.pointyhat/drizzle-2010.05.1561_3.log
 (Apr  2 15:21:51 UTC 2013)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=drizzle


portname:   databases/glom
broken because:

FreeBSD ports which are currently marked forbidden

2013-04-07 Thread linimon 
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, including errors seen on the build farm,
is included below.

portname:   graphics/linux-tiff
forbidden because:  Vulnerable since 2004-10-13,

http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff


portname:   security/sudosh3
forbidden because:  Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo
(55903), replay() function buffer overflow.
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3


portname:   www/linux-flashplugin9
forbidden because:  CVE-2010-1297
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9


portname:   x11-toolkits/linux-pango
forbidden because:  Vulnerable since 2009-05-13,

http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/git to be static

2013-04-07 Thread Matthias Andree 
parv  writes:

> ( Please do carbon copy me the replies for I am not a ports@
>   subscriber. )
>
> Hi there,
>
> Within The Ports, is it possible to compile and install devel/git
> (with subversion & Perl support) as (a collection of) static
> port?
>
> The problem that I want to workaround just appeared: I use git
> (installed with Perl & subversion support) much; subversion is
> currently used only to update FreeBSD ports & src trees.
> subversion-1.7.8 was marked to be vulnerable; I thought I could
> remove 1.7.8 version, and compile & install a newer version.
>
> Turned out git had to be de installed also (sans force) before
> subversion 1.7.8 could be removed. (Or, if subversion was removed
> with force, I would have then needed to do library shuffle to be
> able to run git at all.)

1. For updates,  use utilities such as portupgrade  or portmaster. These
will   handle   the  nitty-gritty   details   of  upgrading   subversion
"underneath" git.

2.  You can  configure Git  to not  depend on  Subversion,  which might,
however, remove all relevant functionality.

cd /usr/ports/devel/git
make config
(disable SVN)
(save options)
make all deinstall install clean

and you are set.

> I could have lived with older version of subversion support
> statically compiled in with git files, (possibly) to be updated
> after newer subversion version was installed **successfully**. Would
> I need to compile git outside of The Ports to achieve the desired
> result?

3.  This is  probably  unnecessary  - Git  only  uses Subversion's  Perl
bindings, and those are loaded anew each and every time you use git-svn,
so updating p5-subversion should suffice.

HTH
Matthias Andree
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

texinfo-5.1.20130313_1 conflicts with emacs-24.3,3

2013-04-07 Thread Marek Rudnicki 
Hi all

I'm trying to install print/texinfo along with editors/emacs using
portmaster and get the following error message:

Installing texinfo-5.1.20130313_1...pkg: texinfo-5.1.20130313_1
conflicts with emacs-24.3,3 (installs files into the same place).
Problematic file: /usr/local/info/info.info.gz


How could I proceed?


I have 9.1-RELEASE, up-to-date port tree and `WITH_PKGNG=yes' in
/etc/make.conf

Best regards
Marek Rudnicki
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2013-04-07 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
net/p5-Daemon-Generic   | 0.82| 0.83
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

If wish to stop receiving portscout reminders, please contact
portsc...@portscout.freebsd.org

Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: No address record

2013-04-07 Thread Anton Shterenlikht 
I'm getting:

# make -C /usr/ports/ fetchindex
fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: No address record
*** [/usr/ports/INDEX-10.bz2] Error code 1

Stop in /usr/ports.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Solved, ingnore: WAS Re: fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2

2013-04-07 Thread Anton Shterenlikht 
my mistake, please ignore

Anton

Date: Fri, 5 Apr 2013 11:37:50 +0100 (BST)
From: Anton Shterenlikht 
To: freebsd-ports@freebsd.org
Subject: fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: No address 
record

I'm getting:

# make -C /usr/ports/ fetchindex
fetch: http://www.FreeBSD.org/ports/INDEX-10.bz2: No address record
*** [/usr/ports/INDEX-10.bz2] Error code 1

Stop in /usr/ports.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Request olvwm

2013-04-07 Thread Lowell Gilbert 
Richard Childers  writes:

> I'm not sure if olvwm is getting any attention - I know there are
> other projects with more users - but I wanted to say, I love that
> window manager.

Do you have any specific requests? The project hasn't had any releases
upstream in years, so the fact that the FreeBSD port hasn't changed much
doesn't seem like a problem...
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports/head@r314338 x11/nvidia-driver

2013-04-07 Thread Alexey Dokuchaev 
On Mon, Apr 01, 2013 at 03:39:37PM +0300, Sergey V. Dyatko wrote:
> On Mon, 1 Apr 2013 05:28:27 -0700
> David Wolfskill  wrote:
> > On Mon, Apr 01, 2013 at 03:24:33PM +0300, Sergey V. Dyatko wrote:
> > > ...
> > > looks like r248084-patch-src-nvidia_subr.c is incomplete
> > > ... 
> > > here complete patch I use on my desktop:
> > > http://svn.freebsd.by/files/patch-src__nvidia_subr.c.txt
> > > 
> > 
> > Please refer to http://www.freebsd.org/cgi/query-pr.cgi?pr=177459
> > (Not my PR, but I have tested that it works for my environment.)
> 
> My bad, I did not take advantage of the power of search, sorry.
> What are the chances of this change to get into the ports tree, before
> 8.4-R ?:)
> If I understand correctly It is one of cases, when commiter may commit
> it without portmgr approval ?

Committed as r315754, sorry for the delay.  If any issues still remain,
please report, thanks!

./danfe
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Request olvwm

2013-04-07 Thread Sergio de Almeida Lenzi 
Em Dom, 2013-04-07 às 10:59 -0400, Lowell Gilbert escreveu:

> Richard Childers  writes:
> 
> > I'm not sure if olvwm is getting any attention - I know there are
> > other projects with more users - but I wanted to say, I love that
> > window manager.
> 
> Do you have any specific requests? The project hasn't had any releases
> upstream in years, so the fact that the FreeBSD port hasn't changed much
> doesn't seem like a problem...
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Olvwm is a good choice for people that wants a small, fast, easy to
configure, and beautiful
look.  Now the only problem is that it does not compile under 64bits...

I tried to fix it but is beyound my knowledge..

If some X guru is  available, please fix it for 64 bits...  


Thanks for your attention,

Sergio
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

kd3libs3 not finding patch

2013-04-07 Thread Super Bisquit 
===>   kdelibs-3.5.10_13 depends on file: /usr/local/sbin/pkg - found
=> kdelibs-3.5-openssl-1.0.0.patch doesn't seem to exist in
/usr/ports/distfiles/KDE.
=> Attempting to fetch
http://oschtan.academ.org/oschtan-overlay/kde-base/kdelibs/files/kdelibs-3.5-openssl-1.0.0.patch
fetch: 
http://oschtan.academ.org/oschtan-overlay/kde-base/kdelibs/files/kdelibs-3.5-openssl-1.0.0.patch:
Not Found
=> Attempting to fetch
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/KDE/kdelibs-3.5-openssl-1.0.0.patch
fetch: 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/KDE/kdelibs-3.5-openssl-1.0.0.patch:
File unavailable (e.g., file not found, no access)
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/KDE and try again.
*** [do-fetch] Error code 1

Stop in /usr/ports/x11/kdelibs3.
*** [lib-depends] Error code 1

Stop in /usr/ports/x11/kdebase3.
*** [install] Error code 1

Stop in /usr/ports/x11/kdebase3.
*** [lib-depends] Error code 1

Stop in /usr/ports/x11/kde3.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Growing list of required(ish) ports

2013-04-07 Thread Robert Simmons 
Are there plans to get the following ports moved into HEAD?

1) ports-mgmt/pkg

2) ports-mgmt/dialog4ports

3) ports-mgmt/portaudit

4) ports-mgmt/portmaster

It seems to me like these belong in the base system.

Also, is there a reason why dialog4ports's functionality wasn't added
to dialog(1) as a switch?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Growing list of required(ish) ports

2013-04-07 Thread Bryan Drewery 
On 4/7/2013 8:47 PM, Robert Simmons wrote:
> Are there plans to get the following ports moved into HEAD?
> 
> 1) ports-mgmt/pkg
> 
> 2) ports-mgmt/dialog4ports
> 
> 3) ports-mgmt/portaudit
> 
> 4) ports-mgmt/portmaster
> 
> It seems to me like these belong in the base system.

On the contrary, the idea is that more and more should come *out of
base* and into ports. Base is very static and stuck in time. By moving
these things into ports, you are able to get updates much simpler. No
need for an errata or security advisory or release. Just updating with
portmaster/pkg upgrade.

portaudit is not needed with pkg, just use 'pkg audit'.

> 
> Also, is there a reason why dialog4ports's functionality wasn't added
> to dialog(1) as a switch?


-- 
Regards,
Bryan Drewery
bdrewery@freenode/EFNet



signature.asc
Description: OpenPGP digital signature

Re: Growing list of required(ish) ports

2013-04-07 Thread Robert Simmons 
On Sun, Apr 7, 2013 at 10:45 PM, Bryan Drewery  wrote:
> On 4/7/2013 8:47 PM, Robert Simmons wrote:
>> Are there plans to get the following ports moved into HEAD?
>>
>> 1) ports-mgmt/pkg
>>
>> 2) ports-mgmt/dialog4ports
>>
>> 3) ports-mgmt/portaudit
>>
>> 4) ports-mgmt/portmaster
>>
>> It seems to me like these belong in the base system.
>
> On the contrary, the idea is that more and more should come *out of
> base* and into ports. Base is very static and stuck in time. By moving
> these things into ports, you are able to get updates much simpler. No
> need for an errata or security advisory or release. Just updating with
> portmaster/pkg upgrade.

I understand where you're coming from, but perhaps there needs to be
movement in both directions.

I may be way off the mark here, but I'd love to spark a discussion
about this.  I think that in general things that are directly FreeBSD
projects belong in base.  Examples would be pkgng, and making
dialog4ports a switch in dialog(1).  Essentially, code that does not
have an upstream should be in base.

On the other hand, there are a number of things that I think should be
pulled out of base.  Some already have ports, and others would need
ports created.  Examples of things to pull out of base are OpenSSL,
Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others.
Code that is typically way behind the upstream project basically.

>
> portaudit is not needed with pkg, just use 'pkg audit'.

I had missed that.  Thanks!

>
>>
>> Also, is there a reason why dialog4ports's functionality wasn't added
>> to dialog(1) as a switch?
>
>
> --
> Regards,
> Bryan Drewery
> bdrewery@freenode/EFNet
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Growing list of required(ish) ports

2013-04-07 Thread Kimmo Paasiala 
On Mon, Apr 8, 2013 at 6:19 AM, Robert Simmons  wrote:
> On Sun, Apr 7, 2013 at 10:45 PM, Bryan Drewery  wrote:
>> On 4/7/2013 8:47 PM, Robert Simmons wrote:
>>> Are there plans to get the following ports moved into HEAD?
>>>
>>> 1) ports-mgmt/pkg
>>>
>>> 2) ports-mgmt/dialog4ports
>>>
>>> 3) ports-mgmt/portaudit
>>>
>>> 4) ports-mgmt/portmaster
>>>
>>> It seems to me like these belong in the base system.
>>
>> On the contrary, the idea is that more and more should come *out of
>> base* and into ports. Base is very static and stuck in time. By moving
>> these things into ports, you are able to get updates much simpler. No
>> need for an errata or security advisory or release. Just updating with
>> portmaster/pkg upgrade.
>
> I understand where you're coming from, but perhaps there needs to be
> movement in both directions.
>
> I may be way off the mark here, but I'd love to spark a discussion
> about this.  I think that in general things that are directly FreeBSD
> projects belong in base.  Examples would be pkgng, and making
> dialog4ports a switch in dialog(1).  Essentially, code that does not
> have an upstream should be in base.
>
> On the other hand, there are a number of things that I think should be
> pulled out of base.  Some already have ports, and others would need
> ports created.  Examples of things to pull out of base are OpenSSL,
> Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others.
> Code that is typically way behind the upstream project basically.
>
>>
>> portaudit is not needed with pkg, just use 'pkg audit'.
>
> I had missed that.  Thanks!
>
>>
>>>
>>> Also, is there a reason why dialog4ports's functionality wasn't added
>>> to dialog(1) as a switch?
>>
>>
>> --
>> Regards,
>> Bryan Drewery
>> bdrewery@freenode/EFNet
>>
> ___

I think Bryan already explained the reasons why pkg should not be in
base, it's an external tool that is not stricly required to get a bare
bones FreeBSD system up and running. Including it in base you create
yet another maintainance burden and would slow down the development of
the ports/packages management tools.

-Kimmo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Free Classified Web Site for All Things Music

2013-04-07 Thread adman 

MusicopiADS.com 
 is a new website that provides free advertising for "All Things
Music" 

If you have a Harp or other musical instrument that you would like to
sell or are trying to find, Or you are a musician, instructor or
dealer who would lke to advertisee your talents, services ormusic for
sale, musicopiADS is a place for your ads. Although I use harps as an
example, any other musical instrument related advertisement can be
placed at musicopiADS 
. Please check this site out and tell everyone you know who may have
interest about musicopiADS. 

Thanks for any consideration you give this. If you do not wish to
receive any more messages, you may unsubscribe using the link below.



--
If you do not want to receive any more newsletters, 
http://www.musicopiads.com/lists/?p=unsubscribe&uid=a2236e17e01942c765c6b3e03dd97516

To update your preferences and to unsubscribe visit
http://www.musicopiads.com/lists/?p=preferences&uid=a2236e17e01942c765c6b3e03dd97516
Forward a Message to Someone
http://www.musicopiads.com/lists/?p=forward&uid=a2236e17e01942c765c6b3e03dd97516&mid=12


--
powered by phpList, www.phplist.com --


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Growing list of required(ish) ports

2013-04-07 Thread Kevin Oberman 
On Sun, Apr 7, 2013 at 8:34 PM, Kimmo Paasiala  wrote:

> On Mon, Apr 8, 2013 at 6:19 AM, Robert Simmons 
> wrote:
> > On Sun, Apr 7, 2013 at 10:45 PM, Bryan Drewery 
> wrote:
> >> On 4/7/2013 8:47 PM, Robert Simmons wrote:
> >>> Are there plans to get the following ports moved into HEAD?
> >>>
> >>> 1) ports-mgmt/pkg
> >>>
> >>> 2) ports-mgmt/dialog4ports
> >>>
> >>> 3) ports-mgmt/portaudit
> >>>
> >>> 4) ports-mgmt/portmaster
> >>>
> >>> It seems to me like these belong in the base system.
> >>
> >> On the contrary, the idea is that more and more should come *out of
> >> base* and into ports. Base is very static and stuck in time. By moving
> >> these things into ports, you are able to get updates much simpler. No
> >> need for an errata or security advisory or release. Just updating with
> >> portmaster/pkg upgrade.
> >
> > I understand where you're coming from, but perhaps there needs to be
> > movement in both directions.
> >
> > I may be way off the mark here, but I'd love to spark a discussion
> > about this.  I think that in general things that are directly FreeBSD
> > projects belong in base.  Examples would be pkgng, and making
> > dialog4ports a switch in dialog(1).  Essentially, code that does not
> > have an upstream should be in base.
> >
> > On the other hand, there are a number of things that I think should be
> > pulled out of base.  Some already have ports, and others would need
> > ports created.  Examples of things to pull out of base are OpenSSL,
> > Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others.
> > Code that is typically way behind the upstream project basically.
> >
> >>
> >> portaudit is not needed with pkg, just use 'pkg audit'.
> >
> > I had missed that.  Thanks!
> >
> >>
> >>>
> >>> Also, is there a reason why dialog4ports's functionality wasn't added
> >>> to dialog(1) as a switch?
> >>
> >>
> >> --
> >> Regards,
> >> Bryan Drewery
> >> bdrewery@freenode/EFNet
> >>
> > ___
>
> I think Bryan already explained the reasons why pkg should not be in
> base, it's an external tool that is not strictly required to get a bare
> bones FreeBSD system up and running. Including it in base you create
> yet another maintainance burden and would slow down the development of
> the ports/packages management tools.
>
> -Kimmo
>

What people seem to miss is that putting tools into the base system
strangles the tools. Look at the difficulty we have seen in updating
openssl. perl was removed from base for exactly that reason. Once something
is in base, it usually can only be updated  on major releases and even then
it can be very complicated. That is a problem for any dynamically changing
tool.

I would love to see BIND removed from base, but most of the things  you
listed really are hard to remove. I know that I don't want to try bringing
up a new install of FreeBSD on a remote system without OpenSSH and that
pulls in openssl.  In the case of many tools, it really turns into a
bikeshed. But i can see no reason to add any of the new packaging tools
simply because it is critical that updates be possible far  more often than
is possible for the base system.
-- 
R. Kevin Oberman, Network Engineer
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Growing list of required(ish) ports

2013-04-07 Thread Robert Simmons 
On Mon, Apr 8, 2013 at 1:11 AM, Kevin Oberman  wrote:
> On Sun, Apr 7, 2013 at 8:34 PM, Kimmo Paasiala  wrote:
>>
>> On Mon, Apr 8, 2013 at 6:19 AM, Robert Simmons 
>> wrote:
>> > On Sun, Apr 7, 2013 at 10:45 PM, Bryan Drewery 
>> > wrote:
>> >> On 4/7/2013 8:47 PM, Robert Simmons wrote:
>> >>> Are there plans to get the following ports moved into HEAD?
>> >>>
>> >>> 1) ports-mgmt/pkg
>> >>>
>> >>> 2) ports-mgmt/dialog4ports
>> >>>
>> >>> 3) ports-mgmt/portaudit
>> >>>
>> >>> 4) ports-mgmt/portmaster
>> >>>
>> >>> It seems to me like these belong in the base system.
>> >>
>> >> On the contrary, the idea is that more and more should come *out of
>> >> base* and into ports. Base is very static and stuck in time. By moving
>> >> these things into ports, you are able to get updates much simpler. No
>> >> need for an errata or security advisory or release. Just updating with
>> >> portmaster/pkg upgrade.
>> >
>> > I understand where you're coming from, but perhaps there needs to be
>> > movement in both directions.
>> >
>> > I may be way off the mark here, but I'd love to spark a discussion
>> > about this.  I think that in general things that are directly FreeBSD
>> > projects belong in base.  Examples would be pkgng, and making
>> > dialog4ports a switch in dialog(1).  Essentially, code that does not
>> > have an upstream should be in base.
>> >
>> > On the other hand, there are a number of things that I think should be
>> > pulled out of base.  Some already have ports, and others would need
>> > ports created.  Examples of things to pull out of base are OpenSSL,
>> > Heimdal, OpenSSH, PF, ntpd, ipfilter, bind, sendmail, and others.
>> > Code that is typically way behind the upstream project basically.
>> >
>> >>
>> >> portaudit is not needed with pkg, just use 'pkg audit'.
>> >
>> > I had missed that.  Thanks!
>> >
>> >>
>> >>>
>> >>> Also, is there a reason why dialog4ports's functionality wasn't added
>> >>> to dialog(1) as a switch?
>> >>
>> >>
>> >> --
>> >> Regards,
>> >> Bryan Drewery
>> >> bdrewery@freenode/EFNet
>> >>
>> > ___
>>
>> I think Bryan already explained the reasons why pkg should not be in
>> base, it's an external tool that is not strictly required to get a bare
>>
>> bones FreeBSD system up and running. Including it in base you create
>> yet another maintainance burden and would slow down the development of
>> the ports/packages management tools.
>>
>> -Kimmo
>
>
> What people seem to miss is that putting tools into the base system
> strangles the tools. Look at the difficulty we have seen in updating
> openssl. perl was removed from base for exactly that reason. Once something
> is in base, it usually can only be updated  on major releases and even then
> it can be very complicated. That is a problem for any dynamically changing
> tool.
>
> I would love to see BIND removed from base, but most of the things  you
> listed really are hard to remove. I know that I don't want to try bringing
> up a new install of FreeBSD on a remote system without OpenSSH and that

OpenSSH is the only one that doesn't follow the same pattern.  It
seems that the port of it has been abandoned going on 2 years.  It is
lagging far far behind 9-stable which looks like DES bumped to 6.1 and
HEAD has been bumped to 6.2p1.

> pulls in openssl.  In the case of many tools, it really turns into a
> bikeshed. But i can see no reason to add any of the new packaging tools
> simply because it is critical that updates be possible far  more often than
> is possible for the base system.
> --
> R. Kevin Oberman, Network Engineer
> E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"