tcl & tk ports on FreeBSD 10 amd64

2013-12-03 Thread Cy Schubert 
Hi,

Sorry for cross posting but this concerns both lists.

Over the last month or so I've been upgrading my prod infrastructure from 9 
to 10. It's mostly complete except for a number of issues. One issue, just 
solved today (circumvented is a better word), is exmh crashing 10.0 on 
amd64 while on i386 there are no issues with exmh.

It appears that the tcl and tk ports (all three of them, 8.4, 8.5, and 8.6) 
will panic 10.0 on amd64 (but not i386) when the ports are built with 
threading support.

I haven't had a chance to look at the dump yet but I had a hunch to test 
the ports without threading support enabled, making the panic go away. If I 
don't get to it in time, here is what I haveFatal trap 9: general 
protection fault while in kernel mode
cpuid = 2; apic id = 02
instruction pointer = 0x20:0x80957aeb
stack pointer   = 0x28:0xfe00f17f9980
frame pointer   = 0x28:0xfe00f17f99a0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 11 (idle: cpu2)
trap number = 9
timeout stopping cpus
panic: general protection fault
cpuid = 2
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
0xfe00f17f9510
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe00f17f95c0
panic() at panic+0x153/frame 0xfe00f17f9640
trap_fatal() at trap_fatal+0x3a2/frame 0xfe00f17f96a0
trap() at trap+0x7bf/frame 0xfe00f17f98c0
calltrap() at calltrap+0x8/frame 0xfe00f17f98c0
--- trap 0x9, rip = 0x80957aeb, rsp = 0xfe00f17f9980, rbp = 
0xfe
00f17f99a0 ---
cpu_idle_hlt() at cpu_idle_hlt+0x2b/frame 0xfe00f17f99a0
cpu_idle() at cpu_idle+0x93/frame 0xfe00f17f99c0
sched_idletd() at sched_idletd+0x1ee/frame 0xfe00f17f9a70
fork_exit() at fork_exit+0x9a/frame 0xfe00f17f9ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe00f17f9ab0
--- trap 0, rip = 0, rsp = 0xfe00f17f9b70, rbp = 0 ---
Uptime: 4m42s
Dumping 522 out of 5932 MB:..4%..13%..22%..31%..43%..53%..62%..71%..83%..92%
 so far,

Tcl/tk are tickling some bug somewhere.

Before anyone suggests memory, I've been able to reproduce this on an Intel 
Core i3 machine with 6 GB and an AMD X2 5000+, also with 6 GB, both in 
amd64 mode. Both systems are dual (or multi) boot. The bug does not exhibit 
itself in i386 mode. It also doesn't exhibit itself when tcl/tk are built 
without thread support.

The only application I know of which tickles the bug is mail/exmh2 (I'm the 
maintainer) when using a threaded tcl/tk.

My 11-CURRENT partition on my laptop is still i386 so I haven't been able 
to reproduce it under 11 with amd64.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
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: pkgng upgrade options

2013-12-03 Thread Kevin Oberman 
On Tue, Dec 3, 2013 at 9:40 AM, Daniel Nebdal  wrote:

> On Tue, Dec 3, 2013 at 11:54 AM, Beeblebrox  wrote:
>
> > >> There should be some OPTONS_FILE_UNSET variables
> > I just left those out and only posted those with " OPTIONS_FILE_SET"
> >
> > >>It's possible that the FreeBSD repo is before your local repo.
> > >>To see the repository order use:  pkg -v -v
> > Yes, the FreeBSD repo is listed first while myrepo is #2. I don't see
> how I
> > can change the order though. Combining all repo info into a single file
> > comes to mind; tried and it seems to break things.
> >
> > The unixODBC / libiodbc conflict is from these two: databases/php5-odbc
>  &
> > databases/php5-pdo_odbc
> > They both have "OPTIONS_FILE_SET+=IODBC" however, so should nat ask for
> > unixODBC
> >
> > The most serious pkg conflict I am seeing is devel/py27-distribute vs.
> > devel/py27-setuptools
> > "pkg set -o devel/py27-distribute:devel/py27-setuptools" has no effect.
> > Only
> > emulators/virtualbox-ose is asking for devel/py-distribute.
> >
> >
> >
> > -
> > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> >
>
> This might be overly trivial, but ... is py27-setuptools already installed,
> by chance? Can you try removing it?
>
>
> --
> Daniel Nebdal
>

The issue with py-distribute/py-setuptools is covered in UPDATING. Just
follow the instructions.

ODBC is a more difficult issue. There are two ALMOST compatible
implementations of OMDB an most ports use one, but a few use the other. Due
to nearly identical name spaces, it is simply not possible to install both.
Most ports can link with either (see make config), so try to get them all
happy with one or the other and get rid of the one not used. Good luck.

-- 
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: pkgng upgrade options

2013-12-03 Thread Daniel Nebdal 
On Tue, Dec 3, 2013 at 11:54 AM, Beeblebrox  wrote:

> >> There should be some OPTONS_FILE_UNSET variables
> I just left those out and only posted those with " OPTIONS_FILE_SET"
>
> >>It's possible that the FreeBSD repo is before your local repo.
> >>To see the repository order use:  pkg -v -v
> Yes, the FreeBSD repo is listed first while myrepo is #2. I don't see how I
> can change the order though. Combining all repo info into a single file
> comes to mind; tried and it seems to break things.
>
> The unixODBC / libiodbc conflict is from these two: databases/php5-odbc  &
> databases/php5-pdo_odbc
> They both have "OPTIONS_FILE_SET+=IODBC" however, so should nat ask for
> unixODBC
>
> The most serious pkg conflict I am seeing is devel/py27-distribute vs.
> devel/py27-setuptools
> "pkg set -o devel/py27-distribute:devel/py27-setuptools" has no effect.
> Only
> emulators/virtualbox-ose is asking for devel/py-distribute.
>
>
>
> -
> FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
>

This might be overly trivial, but ... is py27-setuptools already installed,
by chance? Can you try removing it?


--
Daniel Nebdal
___
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"

[QAT] r335575: 4x leftovers

2013-12-03 Thread Ports-QAT 
Update to 13.11.

Use new lib_depend syntax, sort USES.
Remove left over "USE_DISPLAY=yes" from the switch to USES=display.
GNUchess is no longer needed
Stageify
-

  Build ID:  20131203153600-62442
  Job owner: k...@freebsd.org
  Buildtime: 24 minutes
  Enddate:   Tue, 03 Dec 2013 16:00:09 GMT

  Revision:  r335575
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=335575

-

Port:games/gcompris 13.11

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203153600-62442-234792/gcompris-13.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203153600-62442-234793/gcompris-13.11.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203153600-62442-234794/gcompris-13.11.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203153600-62442-234795/gcompris-13.11.log


--
Buildarchive URL: 
redports 
___
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 via svn, make fetchindex and make compatibility with NetBSD

2013-12-03 Thread Matthew Seaman 
On 12/03/13 12:41, Thomas Mueller wrote:
> Is it necessary to make fetchindex after downloading or updating the ports 
> tree using svn?
> 
> I have new installations of head and 10-stable where I so far can't connect 
> to the Internet, though I can from Linux and NetBSD-current amd64.
> 
> So I use subversion, built on NetBSD from pkgsrc, to checkout and update 
> ports tree as well as system source tree.
> 
> But I believe I can't run "make fetchindex" without Internet connection.
> 
> Now I read that FreeBSD make has switched to bmake in the 10-stable and head 
> branches.
> 
> So could I run "make fetchindex" from NetBSD even if I don't attempt to 
> actually build ports from NetBSD?
> 
> I would have to point the MAKECONF to FreeBSD's /etc/make.conf rather than 
> use NetBSD's /etc/mk.conf which is specific to NetBSD.
> 
> Or is it safe to skip "make fetchindex" entirely?

For most purposes you don't really need a copy of the INDEX.  Some
software -- including portmaster(8), portupgrade(8) -- uses the INDEX
for various purposes, but even then I'm not sure if the presence of the
INDEX is mandatory for those.

If you do need a copy of the index, then you have two choices

   * build your own.  'make index' will thrash your machine for upwards
of twenty minutes, but doesn't require any sort of network access.
(There's also ports-mgmt/p5-FreeBSD-Portindex, but I'm biased because I
wrote it...)

   * Pull down the index from ne of the FreeBSD mirror sites.  'make
fetchindex' is just a wrapper around the command:

  fetch -o INDEX-10.bz2 http://www.FreeBSD.org/ports/INDEX-10.bz2

(or INDEX-11.bz2 for HEAD).  You can use fetch(1), wget(1), curl(1) or
many other applications capable of pulling down a file from a webserver.
 Any Unixoid OS will have the capability to do this.

Building ports on NetBSD is a whole other kettle of fish.  It's not
going to work without a lot of effort to add compatibility changes.
(Getting the ports working on DFly which is much more closely related to
FBSD has been a fairly recent achievement, and that took quite a lot of
local patches.)

Cheers,

Matthew







signature.asc
Description: OpenPGP digital signature

Re: Ports via svn, make fetchindex and make compatibility with NetBSD

2013-12-03 Thread RW 
On Tue, 3 Dec 2013 04:41:17 -0800 (PST)
Thomas Mueller wrote:

> Is it necessary to make fetchindex after downloading or updating the
> ports tree using svn?

Not absolutely, it's needed for portupgrade, port searches, and a number
of utilities use it for speeding various things up.

> I have new installations of head and 10-stable where I so far can't
> connect to the Internet, though I can from Linux and NetBSD-current
> amd64.
> 
> So I use subversion, built on NetBSD from pkgsrc, to checkout and
> update ports tree as well as system source tree.
> 
> But I believe I can't run "make fetchindex" without Internet
> connection.
> 

You can run "make index" instead, it takes about 3 minutes on my
desktop.
___
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"

Ports via svn, make fetchindex and make compatibility with NetBSD

2013-12-03 Thread Thomas Mueller 
Is it necessary to make fetchindex after downloading or updating the ports tree 
using svn?

I have new installations of head and 10-stable where I so far can't connect to 
the Internet, though I can from Linux and NetBSD-current amd64.

So I use subversion, built on NetBSD from pkgsrc, to checkout and update ports 
tree as well as system source tree.

But I believe I can't run "make fetchindex" without Internet connection.

Now I read that FreeBSD make has switched to bmake in the 10-stable and head 
branches.

So could I run "make fetchindex" from NetBSD even if I don't attempt to 
actually build ports from NetBSD?

I would have to point the MAKECONF to FreeBSD's /etc/make.conf rather than use 
NetBSD's /etc/mk.conf which is specific to NetBSD.

Or is it safe to skip "make fetchindex" entirely?

Tom
___
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-12-03 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
+-+
devel/m6811-binutils| 2.15| 2.24
+-+
japanese/skk-jisyo  | 201302  | 201312
+-+
japanese/skk-jisyo-cdb  | 201302  | 201312
+-+


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...@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"

Updating devel/bullet

2013-12-03 Thread Gergely CZUCZY 
Hello,

Could you please update the devel/bullet port to 1.82 (latest as of
now)?

I've tried to do it myself, however some files didn't get installed as
i've noticed when doing the make package.

The changes I've noticed so far:
  1) The release tarball has the revision number, so does the workdir,
  therefore WRKSRC has to be adjusted accordingly
  2) the LICENSE file seemingly got renamed to BulletLicense.txt
  3) files/patch-src_BulletSoftBody_btSoftBodyInternals.h is obsolate,
  the source has this now.

Also, if you can, some options to disable example building/installation
would be nice.

Thanks in advance.

Regards,
Gergely
___
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: Updating devel/bullet

2013-12-03 Thread Gergely CZUCZY 
On Tue, 3 Dec 2013 12:03:56 +0100
Gergely CZUCZY  wrote:

> Hello,
> 
> Could you please update the devel/bullet port to 1.82 (latest as of
> now)?
2.82, sorry. that was a typo above.


> 
> I've tried to do it myself, however some files didn't get installed as
> i've noticed when doing the make package.
> 
> The changes I've noticed so far:
>   1) The release tarball has the revision number, so does the workdir,
>   therefore WRKSRC has to be adjusted accordingly
>   2) the LICENSE file seemingly got renamed to BulletLicense.txt
>   3) files/patch-src_BulletSoftBody_btSoftBodyInternals.h is obsolate,
>   the source has this now.
> 
> Also, if you can, some options to disable example
> building/installation would be nice.
> 
> Thanks in advance.
> 
> Regards,
> Gergely

___
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"

[QAT] r335556: 4x leftovers

2013-12-03 Thread Ports-QAT 
Update to 1.6.2.
-

  Build ID:  20131203105000-19754
  Job owner: k...@freebsd.org
  Buildtime: 13 minutes
  Enddate:   Tue, 03 Dec 2013 11:03:28 GMT

  Revision:  r335556
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=335556

-

Port:x11-themes/mate-themes 1.6.2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203105000-19754-234700/mate-themes-1.6.2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203105000-19754-234701/mate-themes-1.6.2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203105000-19754-234702/mate-themes-1.6.2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20131203105000-19754-234703/mate-themes-1.6.2.log


--
Buildarchive URL: 
redports 
___
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: pkg install from ports list

2013-12-03 Thread Beeblebrox 
@ Oli: The code you posted is most likely correct, as I get the same error if
I do it manually from the terminal:
# pkg install aaa/port1 bbb/port2 ccc/port3 etc..
I am slicing the list into smaller pieces and running the code you posted on
the smaller slices. It works, as long as the list does not contain a port
with some kind of issue. The issues appear to be:
* Dependent port is one of conflicting ports (py27-setuptools for example)
* If the list already contains the dependent port (Not always, seems to loop
on its self for some however)

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/pkg-install-from-ports-list-tp5865626p5865659.html
Sent from the freebsd-ports mailing list archive at Nabble.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: pkgng upgrade options

2013-12-03 Thread Beeblebrox 
>> There should be some OPTONS_FILE_UNSET variables
I just left those out and only posted those with " OPTIONS_FILE_SET"

>>It's possible that the FreeBSD repo is before your local repo.
>>To see the repository order use:  pkg -v -v
Yes, the FreeBSD repo is listed first while myrepo is #2. I don't see how I
can change the order though. Combining all repo info into a single file
comes to mind; tried and it seems to break things.

The unixODBC / libiodbc conflict is from these two: databases/php5-odbc  & 
databases/php5-pdo_odbc
They both have "OPTIONS_FILE_SET+=IODBC" however, so should nat ask for
unixODBC

The most serious pkg conflict I am seeing is devel/py27-distribute vs.
devel/py27-setuptools
"pkg set -o devel/py27-distribute:devel/py27-setuptools" has no effect. Only
emulators/virtualbox-ose is asking for devel/py-distribute.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/pkgng-upgrade-options-tp5862526p5865658.html
Sent from the freebsd-ports mailing list archive at Nabble.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: Building specific ports with gcc in 10.0

2013-12-03 Thread Matthieu Volat 

Le 3 déc. 2013 à 00:00, Matthias Andree  a écrit :

> Signé partie PGP
> Am 13.11.2013 19:50, schrieb Matthieu Volat:
> > Hi everybody,
> >
> > With the 10.0 release becoming more and more tangible, I tried to switch 
> > one laptop to 10.0-BETA3 and see how it would go.
> >
> > I fumbled into a problem that I have a hard time to resolve: I would like 
> > to build graphics/darktable with gcc (lang/gcc46 to be precise, through the 
> > USE_GCC system) to benefit from openmp support.
> >
> > Here's the problem : graphics/darktable, mostly C, uses graphics/exiv2 
> > which is written in C++, but built with clang++/libc++. So when I try to 
> > build graphics/darktable, I get errors of unresolved symbols from exiv2 
> > library:
> >
> > libdarktable.so: undefined reference to 
> > `Exiv2::XmpProperties::registerNs(std::basic_string > std::char_traits, std::allocator > const&, 
> > std::basic_string, std::allocator > 
> > const&)'
> > libdarktable.so: undefined reference to 
> > `Exiv2::XmpParser::encode(std::basic_string, 
> > std::allocator >&, Exiv2::XmpData const&, unsigned short, unsigned 
> > int)'
> > libdarktable.so: undefined reference to
> > `Exiv2::ExifData::operator[](std::basic_string > std::char_traits, std::allocator > const&)'
> > [...]
> >
> > I suppose this comes from symbol naming conventions between clang++/libc++ 
> > and g++/libstdc++ (wasn't C++ ABI supposed to be standard? I guess not). If 
> > I build exiv2 with g++, I can build darktable, but I feel this way of doing 
> > things will be a PITA in the future.
> >
> > Does anybody knowledgeable with gcc know how to manage those issues?
> >
> 
> An older post, but since it's unanswered, here goes:
> 
> I'd personally avoid mixing C++ libraries with software that complex,
> not only to spare myself the bloat, but also to avoid subtle crashes.
> 
> I have run into the same issue with graphics/rawtherapee, and have
> "solved" it by ignoring OpenMP for now on systems that default to clang,
> and use clang to build rawtherapee on those. Not sure how well it works,
> haven't received feedback anywhere yet.
> 
> Solving this for good would require changes to the ports infrastructure
> where a C++-based port can state "I need libstdc++ ABI versions of
> library FOO and BAR", or, more generally, where:
> 
> 1. multiple libraries with different C++ ABI versions can be installed
>(possibly only installing the differing ABI if there is already an
>installation, as a later refinement)
> 
>If it required two full installations (with distinct prefix) for the
>nonce, I could live with that.
> 
> 2. ports can choose to depend on a particular ABI version, per their
>compiler preference, so that rawtherapee or darktable, if they set
>USE_GCC or equivalent, will automatically depend on the libstdc++
>ABI versions of libraries, and if necessary, install them.
> 
> We may also need to build/install subpackages, or multiple packages from
> the same port.  I guess with STAGEDIR this has become somewhat closer to
> realizable.

Thanks, giving up on OpenMP in this case (and praying that no other c++ port 
will trigger this problem) was also my conclusion… That or begin with 
installing gcc from ports and then using it as port compiler, but I've grown to 
like clang :)

One other possible solution would be to manage having gcc to not use its c++ 
header/libstdc++, but the base headers and libc++. I see that one debian 
developer seems to achieved that 
(http://sylvestre.ledru.info/blog/2012/08/15/libc_new_c_standard_library_in_debian).

> 
> 
> Side remarks:
> 
> a. We dug up three clang bugs in 10-STABLE so far. One "only" causes
> excessive compile times, two cause the compiler to run out of memory.
> dim@ helped dig up references, reduce the test cases to reasonable size;
> these issues have all been reported upstream unless the upstream
> bugtracker already knew them.
> 
> b. Apparently Intel donated OpenMP to clang back in the clang-3.1 days.
> I hope that these be integrated into clang, but haven't seen much
> conclusive material.

There were some news a while ago that it was updated to clang 3.3 and the llvm 
project seems to like the idea as they put it in their project list : 
http://openmp.llvm.org/ . The problem is that it requires the intel openmp 
runtime that only build with gcc/icc for now, I tried to add clang support but 
it's not so trivial...


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: pkg install from ports list

2013-12-03 Thread Beeblebrox 
>>Oli Hauer wrote:
>> Using the $cat/$port notation has always worked.

Yes, but it seems not to work in "list file" situations

>> Not tested, but I suspect this will work.
>> pkg install `awk '{printf "%s ", $1}' $path/to/poudriere/portlist`

SAMPLE OUTPUT:
e17-module-winlist-ng-20130510 already installed
e17-module-winselector-20130510 already installed
e17-modules-20130510 already installed
pkg: No packages matching 'x11-wm/enlightenment' available in the
repositories

My pkg repo shows: pkg/All/enlightenment-0.17.5,2.txz

# pkg install x11-wm/enlightenment
Updating repository catalogue
..stuff.
enlightenment-0.17.5,2 already installed

I get the "No packages matching 'foo/bar' available in the repositories"
message for most of what is in the list, even when I do:
# pkg install -r myrepo `awk '{printf "%s ", $1}'
$path/to/poudriere/portlist`

Thanks and Regards.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/pkg-install-from-ports-list-tp5865626p5865641.html
Sent from the freebsd-ports mailing list archive at Nabble.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"