From owner-freebsd-ports@freebsd.org Sun Oct 1 03:46:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFC2FE35DA4 for ; Sun, 1 Oct 2017 03:46:26 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3B4B651E8 for ; Sun, 1 Oct 2017 03:46:25 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 221F3335; Sat, 30 Sep 2017 22:46:25 -0500 (CDT) Date: Sat, 30 Sep 2017 22:46:24 -0500 From: Mark Linimon To: Kevin Oberman Cc: FreeBSD Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171001034623.GB27224@lonesome.com> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 03:46:26 -0000 On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote: > as it makes FreeBSD unusable for those of us with only "small" > systems where the weight of poudriere simply can't be justified. I'm confused. I have been using poudriere for several years to build sparc64 packages. 2 * single core 1.5GHz CPU, 16GB RAM, 2 * 72GB SCSI-3 disks. Yes, it can get disk-bound, especially I am not using ZFS. No, it's not particularly fast. Yes, the machine is solely dedicated to this task. I do believe poudriere will struggle on the smaller ARM boards, solely due to the RAM limitations. I intend to do some further investigation. mcl From owner-freebsd-ports@freebsd.org Sun Oct 1 04:02:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E4CBE363F9 for ; Sun, 1 Oct 2017 04:02:31 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0331265906; Sun, 1 Oct 2017 04:02:30 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 87F9C335; Sat, 30 Sep 2017 23:02:29 -0500 (CDT) Date: Sat, 30 Sep 2017 23:02:28 -0500 From: Mark Linimon To: Don Lewis Cc: rkoberman@gmail.com, freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171001040228.GC27224@lonesome.com> References: <201709301930.v8UJUERE025933@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201709301930.v8UJUERE025933@gw.catspoiler.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 04:02:31 -0000 On Sat, Sep 30, 2017 at 12:30:14PM -0700, Don Lewis wrote: > it illustrates the problem of synth being the only real > consumer of the ADA toolchain (which John also maintained) > on FreeBSD. It's only fair to point out that John did a great deal of work on Ada on FreeBSD. However ... > Another issue is that synth is only available on x86 because that > is what the toolchain limits it to This, to me, is what always stuck in my craw. I think John may have done some work on Ada on armv6 and/or aarch64 but I would have to go check to be sure. There is a _possibility_ that with sufficient effort it could be made to work there. But AFAICT there was never any realistic chance it could work on mips, powerpc, or sparc64. Now, you might claim those aren't deal-breakers, but IMVHO not having it working on both armv6 and aarch64, at production quality, *is* one -- those two need to be first-class citizens going forward (e.g. for 12.0). mcl From owner-freebsd-ports@freebsd.org Sun Oct 1 04:14:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C93DE367CD for ; Sun, 1 Oct 2017 04:14:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A41865D52 for ; Sun, 1 Oct 2017 04:14:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id E791B335; Sat, 30 Sep 2017 23:14:05 -0500 (CDT) Date: Sat, 30 Sep 2017 23:14:04 -0500 From: Mark Linimon To: Kevin Oberman Cc: FreeBSD Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171001041404.GD27224@lonesome.com> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 04:14:07 -0000 On Sat, Sep 30, 2017 at 10:06:17AM -0700, Kevin Oberman wrote: > It is unclear to me whether this was in regard to pots > to the mailing lists or included private responses to > the mail list discussions. I know the former is true, not sure about the latter, but he also used the bugs database in a fashion I can only describe as caustic. (That drove at least one person away from the project.) John is ably qualified technically. If you agree with him on such things as goals and design decisions, he is easy to work with. But my experience was that if you did not, you were in for a long fight. Obvious disclaimer: I was in the latter category. People will have to come to their own conclusions. mcl From owner-freebsd-ports@freebsd.org Sun Oct 1 06:56:12 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A71A2E30AF4 for ; Sun, 1 Oct 2017 06:56:12 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6ADD876A2E for ; Sun, 1 Oct 2017 06:56:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29203 invoked from network); 1 Oct 2017 06:56:04 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 1 Oct 2017 06:56:04 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sun, 01 Oct 2017 02:56:04 -0400 (EDT) Received: (qmail 16328 invoked from network); 1 Oct 2017 06:56:03 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 1 Oct 2017 06:56:03 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 03AADEC8143; Sat, 30 Sep 2017 23:56:02 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: head -r324071 system clang 5 based powerpc64 building ports: lang/gcc7 messed up by a matching name vec_step? [renaming in tree-vect-loop.c avoids the issue] Date: Sat, 30 Sep 2017 23:56:02 -0700 References: <47941770-2A08-4524-8BCC-3FE1D2F3B7F2@dsl-only.net> <54D59906-80CE-4936-B5FD-BCCD87A09F76@dsl-only.net> <750985A4-754C-402A-A5D2-5B48738598CD@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain , FreeBSD Ports , Gerald Pfeifer In-Reply-To: <750985A4-754C-402A-A5D2-5B48738598CD@dsl-only.net> Message-Id: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 06:56:12 -0000 [If work/gcc-7.2.0/gcc/tree-vect-loop.c avoids the name vec_step then it avoids the conflicting use for altivec support in the powerpc64 context. I used vec_step_renamed as the name in work/gcc-7.2.0/gcc/tree-vect-loop.c instead. Similarly for devel/powerpc64-gcc and likely other variants.] On 2017-Sep-29, at 12:14 PM, Mark Millard wrote: > Summary of later additions: >=20 > devel/powerpc64-gcc has the same problem as gcc7 > in this clang-based powerpc64. >=20 > My note about using gcc 4.2.1 for the kernel > build was wrong. (My 32-bit powerpc builds > are that way, not the powerpc64 ones.) >=20 > On 2017-Sep-29, at 1:51 AM, Mark Millard = wrote: >=20 >> [Looks like gcc7 might be causing its own problem >> via a vec_step macro name in its altivec.h .] >>=20 >> On 2017-Sep-29, at 1:14 AM, Mark Millard = wrote: >>=20 >>> I attempted a poudriere based build of some >>> ports and the gcc7 build involved failed >>> with the following sorts of notices: >=20 > devel/powerpc64-gcc has the same problem as gcc7 > in this clang-based powerpc64 >=20 >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:3835:27: = error: expected unqualified-id >>> tree new_vec, vec_init, vec_step, t; >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:3835:26: = error: expected ';' at end of declaration >>> tree new_vec, vec_init, vec_step, t; >>> ^ >>> ; >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:3983:3: = error: use of undeclared identifier 't' >>> t =3D unshare_expr (new_name); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:3988:49: = error: use of undeclared identifier 't' >>> new_vec =3D build_vector_from_val (stepvectype, t); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:3989:12: = error: expected expression >>> vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, NULL); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:4011:75: = error: expected expression >>> new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, induc_def, = vec_step); >>> = ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:4048:7: = error: use of undeclared identifier 't' >>> t =3D unshare_expr (new_name); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:4051:53: = error: use of undeclared identifier 't' >>> new_vec =3D build_vector_from_val (stepvectype, t); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:4052:16: = error: expected expression >>> vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, = NULL); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:4060:25: = error: expected expression >>> vec_def, vec_step); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:6327:9: = error: expected unqualified-id >>> tree vec_step =3D build_vector_from_val = (cr_index_vector_type, step); >>> ^ >>> = /wrkdirs/usr/ports/lang/gcc7/work/gcc-7.2.0/gcc/tree-vect-loop.c:6333:36: = error: expected expression >>> create_iv (series_vect, vec_step, NULL_TREE, loop, &incr_gsi, >>> ^ >>> 50 warnings and 12 errors generated. >>> gmake[3]: *** [Makefile:1099: tree-vect-loop.o] Error 1 >>> gmake[3]: *** Waiting for unfinished jobs.... >>> 42 warnings generated. >>> 51 warnings generated. >>> 50 warnings generated. >>> rm gfortran.pod gcc.pod >>> gmake[3]: Leaving directory = '/wrkdirs/usr/ports/lang/gcc7/work/.build/gcc' >>> gmake[2]: *** [Makefile:4225: all-gcc] Error 2 >>> gmake[2]: Leaving directory = '/wrkdirs/usr/ports/lang/gcc7/work/.build' >>> gmake[1]: *** [Makefile:893: all] Error 2 >>> gmake[1]: Leaving directory = '/wrkdirs/usr/ports/lang/gcc7/work/.build' >>> =3D=3D=3D> Compilation failed unexpectedly. >>> Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the = failure to >>> the maintainer. >>> *** Error code 1 >>>=20 >>> Stop. >>> make: stopped in /usr/ports/lang/gcc7 >>> =3D>> Cleaning up wrkdir >>> =3D=3D=3D> Cleaning for gcc7-7.2.0_1 >>> build of lang/gcc7 | gcc7-7.2.0_1 ended at Fri Sep 29 00:22:00 PDT = 2017 >>> build time: 00:29:27 >>> !!! build failure encountered !!! >>=20 >> Turns out that there is: >>=20 >> # grep -r "\" ~/poudriere_failure/lang_gcc7/ | more >> . . . >> = /root/poudriere_failure/lang_gcc7/work/gcc-7.2.0/gcc/config/rs6000/altivec= .h:/* Given the vec_step of a type, return the corresponding bool type. = */ >> = /root/poudriere_failure/lang_gcc7/work/gcc-7.2.0/gcc/config/rs6000/altivec= .h:typename __altivec_bool_ret ::__ret \ >> = /root/poudriere_failure/lang_gcc7/work/gcc-7.2.0/gcc/config/rs6000/altivec= .h: to #define vec_step to __builtin_vec_step. */ >> = /root/poudriere_failure/lang_gcc7/work/gcc-7.2.0/gcc/config/rs6000/altivec= .h:#define vec_step(x) __builtin_vec_step (* (__typeof__ (x) *) 0) >> . . . >>=20 >> ( config/s390/vecintrin.h has something similar.) It turns out that avoiding the non-global identifier vec_step allows getting past this issue. For lang/gcc7 : # more /usr/ports/lang/gcc7/files/patch-gcc_tree-vect-loop.c=20 --- gcc/tree-vect-loop.c.orig 2017-03-28 15:35:56 UTC +++ gcc/tree-vect-loop.c @@ -3832,7 +3832,7 @@ get_initial_def_for_induction (gimple *iv_phi) edge pe =3D loop_preheader_edge (loop); struct loop *iv_loop; basic_block new_bb; - tree new_vec, vec_init, vec_step, t; + tree new_vec, vec_init, vec_step_renamed, t; tree new_name; gimple *new_stmt; gphi *induction_phi; @@ -3986,7 +3986,7 @@ get_initial_def_for_induction (gimple *iv_phi) stepvectype =3D get_vectype_for_scalar_type (TREE_TYPE (new_name)); gcc_assert (stepvectype); new_vec =3D build_vector_from_val (stepvectype, t); - vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, NULL); + vec_step_renamed =3D vect_init_vector (iv_phi, new_vec, stepvectype, = NULL); =20 =20 /* Create the following def-use cycle: @@ -4008,7 +4008,7 @@ get_initial_def_for_induction (gimple *iv_phi) induc_def =3D PHI_RESULT (induction_phi); =20 /* Create the iv update inside the loop */ - new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, induc_def, = vec_step); + new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, induc_def, = vec_step_renamed); vec_def =3D make_ssa_name (vec_dest, new_stmt); gimple_assign_set_lhs (new_stmt, vec_def); gsi_insert_before (&si, new_stmt, GSI_SAME_STMT); @@ -4049,7 +4049,7 @@ get_initial_def_for_induction (gimple *iv_phi) gcc_assert (CONSTANT_CLASS_P (new_name) || TREE_CODE (new_name) =3D=3D SSA_NAME); new_vec =3D build_vector_from_val (stepvectype, t); - vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, = NULL); + vec_step_renamed =3D vect_init_vector (iv_phi, new_vec, = stepvectype, NULL); =20 vec_def =3D induc_def; prev_stmt_vinfo =3D vinfo_for_stmt (induction_phi); @@ -4057,7 +4057,7 @@ get_initial_def_for_induction (gimple *iv_phi) { /* vec_i =3D vec_prev + vec_step */ new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, - vec_def, vec_step); + vec_def, vec_step_renamed); vec_def =3D make_ssa_name (vec_dest, new_stmt); gimple_assign_set_lhs (new_stmt, vec_def); =20 @@ -6324,13 +6324,13 @@ vectorizable_reduction (gimple *stmt, = gimple_stmt_iter =20 /* Create a vector of the step value. */ tree step =3D build_int_cst (cr_index_scalar_type, = nunits_out); - tree vec_step =3D build_vector_from_val (cr_index_vector_type, = step); + tree vec_step_renamed =3D build_vector_from_val = (cr_index_vector_type, step); =20 /* Create an induction variable. */ gimple_stmt_iterator incr_gsi; bool insert_after; standard_iv_increment_position (loop, &incr_gsi, = &insert_after); - create_iv (series_vect, vec_step, NULL_TREE, loop, &incr_gsi, + create_iv (series_vect, vec_step_renamed, NULL_TREE, loop, = &incr_gsi, insert_after, &indx_before_incr, &indx_after_incr); =20 /* Next create a new phi node vector (NEW_PHI_TREE) which = starts For devel/powerpc64-gcc: # more /usr/ports/devel/powerpc64-gcc/files/patch-gcc_tree-vect-loop.c --- gcc/tree-vect-loop.c.orig 2016-06-01 16:06:29 UTC +++ gcc/tree-vect-loop.c @@ -3702,7 +3702,7 @@ get_initial_def_for_induction (gimple *iv_phi) edge pe =3D loop_preheader_edge (loop); struct loop *iv_loop; basic_block new_bb; - tree new_vec, vec_init, vec_step, t; + tree new_vec, vec_init, vec_step_renamed, t; tree new_name; gimple *new_stmt; gphi *induction_phi; @@ -3856,7 +3856,7 @@ get_initial_def_for_induction (gimple *iv_phi) stepvectype =3D get_vectype_for_scalar_type (TREE_TYPE (new_name)); gcc_assert (stepvectype); new_vec =3D build_vector_from_val (stepvectype, t); - vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, NULL); + vec_step_renamed =3D vect_init_vector (iv_phi, new_vec, stepvectype, = NULL); =20 =20 /* Create the following def-use cycle: @@ -3878,7 +3878,7 @@ get_initial_def_for_induction (gimple *iv_phi) induc_def =3D PHI_RESULT (induction_phi); =20 /* Create the iv update inside the loop */ - new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, induc_def, = vec_step); + new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, induc_def, = vec_step_renamed); vec_def =3D make_ssa_name (vec_dest, new_stmt); gimple_assign_set_lhs (new_stmt, vec_def); gsi_insert_before (&si, new_stmt, GSI_SAME_STMT); @@ -3919,7 +3919,7 @@ get_initial_def_for_induction (gimple *iv_phi) gcc_assert (CONSTANT_CLASS_P (new_name) || TREE_CODE (new_name) =3D=3D SSA_NAME); new_vec =3D build_vector_from_val (stepvectype, t); - vec_step =3D vect_init_vector (iv_phi, new_vec, stepvectype, = NULL); + vec_step_renamed =3D vect_init_vector (iv_phi, new_vec, = stepvectype, NULL); =20 vec_def =3D induc_def; prev_stmt_vinfo =3D vinfo_for_stmt (induction_phi); @@ -3927,7 +3927,7 @@ get_initial_def_for_induction (gimple *iv_phi) { /* vec_i =3D vec_prev + vec_step */ new_stmt =3D gimple_build_assign (vec_dest, PLUS_EXPR, - vec_def, vec_step); + vec_def, vec_step_renamed); vec_def =3D make_ssa_name (vec_dest, new_stmt); gimple_assign_set_lhs (new_stmt, vec_def); =20 @@ -6129,13 +6129,13 @@ vectorizable_reduction (gimple *stmt, = gimple_stmt_iter =20 /* Create a vector of the step value. */ tree step =3D build_int_cst (cr_index_scalar_type, = nunits_out); - tree vec_step =3D build_vector_from_val (cr_index_vector_type, = step); + tree vec_step_renamed =3D build_vector_from_val = (cr_index_vector_type, step); =20 /* Create an induction variable. */ gimple_stmt_iterator incr_gsi; bool insert_after; standard_iv_increment_position (loop, &incr_gsi, = &insert_after); - create_iv (series_vect, vec_step, NULL_TREE, loop, &incr_gsi, + create_iv (series_vect, vec_step_renamed, NULL_TREE, loop, = &incr_gsi, insert_after, &indx_before_incr, &indx_after_incr); =20 /* Next create a new phi node vector (NEW_PHI_TREE) which = starts >>> FYI: >>>=20 >>> # grep -r "\" /usr/src/* | more >>> /usr/src/contrib/llvm/tools/clang/lib/AST/ASTDumper.cpp: OS << " = vec_step"; >>> /usr/src/contrib/llvm/tools/clang/lib/AST/StmtPrinter.cpp: OS << = "vec_step"; >>> /usr/src/contrib/llvm/tools/clang/lib/AST/ExprConstant.cpp:/// = VisitUnaryExprOrTypeTraitExpr - Evaluate a sizeof, alignof or vec_step = with >>> /usr/src/contrib/llvm/tools/clang/lib/AST/ExprConstant.cpp: // = The vec_step built-in functions that take a 3-component >>> /usr/src/contrib/llvm/tools/clang/lib/AST/ItaniumMangle.cpp: = "cannot yet mangle vec_step expression"); >>> /usr/src/contrib/llvm/tools/clang/lib/Headers/opencl-c.h: * by = vec_step(gentypem). The shuffle mask operand >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp: case = tok::kw_vec_step: // unary-expression: OpenCL 'vec_step' expression >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp:/// = vec_step and we are at the start of an expression or a parenthesized >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp:/// = [OpenCL 1.1 6.11.12] vec_step built-in function: >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp:/// = vec_step ( expressions ) >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp:/// = vec_step ( type-name ) >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp: = "Not a typeof/sizeof/alignof/vec_step expression!"); >>> /usr/src/contrib/llvm/tools/clang/lib/Parse/ParseExpr.cpp: = "Not a sizeof/alignof/vec_step expression!"); >>> /usr/src/contrib/llvm/tools/clang/lib/Sema/SemaExpr.cpp: // [OpenCL = 1.1 6.11.12] "The vec_step built-in function takes a built-in >>> /usr/src/contrib/llvm/tools/clang/lib/Sema/TreeTransform.h: /// = \brief Build a new sizeof, alignof or vec_step expression with a >>> /usr/src/contrib/llvm/tools/clang/include/clang/AST/Expr.h:/// = vec_step (OpenCL 1.1 6.11.12). >>> = /usr/src/contrib/llvm/tools/clang/include/clang/ASTMatchers/ASTMatchers.h:= /// \brief Matches sizeof (C99), alignof (C++11) and vec_step (OpenCL) >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "invalid application of '%select{sizeof|alignof|vec_step}0' to a " >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "invalid application of '%select{sizeof|alignof|vec_step}0' to a = void " >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "invalid application of = '%select{sizeof|alignof|vec_step|__builtin_omp_required_simd_align}0' to = a void type">; >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "invalid application of = '%select{sizeof|alignof|vec_step|__builtin_omp_required_simd_align}0' to = an " >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "invalid application of = '%select{sizeof|alignof|vec_step|__builtin_omp_required_simd_align}0' to = a " >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/DiagnosticSemaKinds.= td: "'vec_step' requires built-in scalar or vector type, %0 invalid">; >>> = /usr/src/contrib/llvm/tools/clang/include/clang/Basic/TokenKinds.def:KEYWO= RD(vec_step , KEYOPENCL|KEYALTIVEC|KEYZVECTOR) >>> /usr/src/contrib/gcc/config/rs6000/altivec.h:/* Given the vec_step = of a type, return the corresponding bool type. */ >>> /usr/src/contrib/gcc/config/rs6000/altivec.h:typename = __altivec_bool_ret ::__ret \ >>> /usr/src/contrib/gcc/config/rs6000/altivec.h: to #define vec_step = to __builtin_vec_step. */ >>> /usr/src/contrib/gcc/config/rs6000/altivec.h:#define vec_step(x) = __builtin_vec_step (* (__typeof__ (x) *) 0) >>> /usr/src/contrib/gcc/ChangeLog-2002: * config/rs6000/altivec.h = (vec_step): Remove extraneous >>> /usr/src/contrib/gcc/ChangeLog-2002: (vec_step): Implement for = C++. >>>=20 >>>=20 >>> Context: >>>=20 >>> # uname -apKU >>> FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r324071M powerpc = powerpc64 1200047 1200047 >>>=20 >>> Built via amd64 -> powerpc64 cross build, using clang >>> for buildworld: >>>=20 >>> [Note: The kernel was built with gcc 4.2.1 .] >=20 > Wrong: I was thinking of the powerpc (32- bit) build > when I wrote that. powerpc64 is a pure clang based build. >=20 >>>=20 >>> # poudriere jail -l >>> JAILNAME VERSION ARCH METHOD TIMESTAMP = PATH >>> FBSDpowerpc64 12.0-CURRENT powerpc.powerpc64 null 2017-09-28 = 20:55:01 /usr/obj/DESTDIRs/clang-powerpc64-installworld_altbinutils-poud >>>=20 >>> (It is using /usr/src .) >>>=20 >>> # poudriere ports -l >>> PORTSTREE METHOD TIMESTAMP PATH >>> default null 2017-09-28 17:04:57 /usr/ports >>>=20 >>>=20 >>> # more = ~/src.configs/src.conf.powerpc64-clang_altbinutils-bootstrap.amd64-host=20= >>> TO_TYPE=3Dpowerpc64 >>> TOOLS_TO_TYPE=3D${TO_TYPE} >>> VERSION_CONTEXT=3D12.0 >>> # >>> KERNCONF=3DGENERIC64vtsc-NODBG >>> TARGET=3Dpowerpc >>> .if ${.MAKE.LEVEL} =3D=3D 0 >>> TARGET_ARCH=3D${TO_TYPE} >>> .export TARGET_ARCH >>> .endif >>> # >>> WITH_CROSS_COMPILER=3D >>> WITHOUT_SYSTEM_COMPILER=3D >>> # >>> WITH_LIBCPLUSPLUS=3D >>> WITHOUT_BINUTILS_BOOTSTRAP=3D >>> WITH_ELFTOOLCHAIN_BOOTSTRAP=3D >>> WITH_CLANG_BOOTSTRAP=3D >>> WITH_CLANG=3D >>> WITH_CLANG_IS_CC=3D >>> WITH_CLANG_FULL=3D >>> WITH_CLANG_EXTRAS=3D >>> WITHOUT_LLD_BOOTSTRAP=3D >>> WITH_LLD=3D >>> WITHOUT_LLD_IS_LD=3D >>> WITH_LLDB=3D >>> # >>> WITH_BOOT=3D >>> WITH_LIB32=3D >>> # >>> WITHOUT_GCC_BOOTSTRAP=3D >>> WITHOUT_GCC=3D >>> WITHOUT_GCC_IS_CC=3D >>> WITHOUT_GNUCXX=3D >>> # >>> NO_WERROR=3D >>> MALLOC_PRODUCTION=3D >>> # >>> # Avoid converts between pointers to integer types with different = sign [-Werror,-Wpointer-sign] >>> # and such from blocking the build. >>> WERROR=3D >>> # >>> WITH_REPRODUCIBLE_BUILD=3D >>> WITH_DEBUG_FILES=3D >>> # >>> # >>> # For TO (so-called "cross") stages . . . >>> # So-called-cross via ${TO_TYPE}-xtoolchain-gcc/${TO_TYPE}-gcc. . . >>> # TOOLS_TO_TYPE based on ${TO_TYPE}-xtoolchain-gcc related binutils. = . . >>> # >>> CROSS_BINUTILS_PREFIX=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ >>> .if ${.MAKE.LEVEL} =3D=3D 0 >>> # >>> # Note: The WITH_CROSS_COMPILER picks up the CROSS_BINUTILS_PREFIX >>> # binding automatically. >>> # >>> XAS=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/as >>> XAR=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ar >>> XNM=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/nm >>> XOBJCOPY=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/objcopy >>> XOBJDUMP=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/objdump >>> XRANLIB=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ranlib >>> XSIZE=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/size >>> #NO-SUCH: XSTRINGS=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/strings >>> XSTRINGS=3D/usr/local/bin/${TOOLS_TO_TYPE}-freebsd-strings >>> .export XAS >>> .export XAR >>> .export XNM >>> .export XOBJCOPY >>> .export XOBJDUMP >>> .export XRANLIB >>> .export XSIZE >>> .export XSTRINGS >>> XLD=3D/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ld >>> .export XLD >>> .endif >>>=20 >>> # svnlite status /usr/src/ | sort >>> ? /usr/src/sys/amd64/conf/GENERIC-DBG >>> ? /usr/src/sys/amd64/conf/GENERIC-NODBG >>> ? /usr/src/sys/arm/conf/GENERIC-DBG >>> ? /usr/src/sys/arm/conf/GENERIC-NODBG >>> ? /usr/src/sys/arm64/conf/GENERIC-DBG >>> ? /usr/src/sys/arm64/conf/GENERIC-NODBG >>> ? /usr/src/sys/powerpc/conf/GENERIC64vtsc-DBG >>> ? /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG >>> ? /usr/src/sys/powerpc/conf/GENERICvtsc-DBG >>> ? /usr/src/sys/powerpc/conf/GENERICvtsc-NODBG >>> M = /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp >>> M /usr/src/contrib/llvm/tools/lld/ELF/Arch/PPC64.cpp >>> M /usr/src/crypto/openssl/crypto/armcap.c >>> M /usr/src/lib/Makefile >>> M /usr/src/lib/libkvm/kvm_powerpc.c >>> M /usr/src/lib/libkvm/kvm_private.c >>> M /usr/src/sys/arm64/arm64/identcpu.c >>> M /usr/src/sys/arm64/arm64/mp_machdep.c >>> M /usr/src/sys/boot/ofw/Makefile.inc >>> M /usr/src/sys/boot/powerpc/Makefile.inc >>> M /usr/src/sys/boot/powerpc/boot1.chrp/Makefile >>> M /usr/src/sys/boot/powerpc/kboot/Makefile >>> M /usr/src/sys/boot/uboot/Makefile.inc >>> M /usr/src/sys/conf/kmod.mk >>> M /usr/src/sys/conf/ldscript.powerpc >>> M /usr/src/sys/ddb/db_main.c >>> M /usr/src/sys/ddb/db_script.c >>> M /usr/src/sys/kern/subr_pcpu.c >>> M /usr/src/sys/powerpc/aim/mmu_oea64.c >>> M /usr/src/sys/powerpc/ofw/ofw_machdep.c >>> M /usr/src/sys/powerpc/powerpc/interrupt.c >>> M /usr/src/sys/powerpc/powerpc/mp_machdep.c >>> M /usr/src/sys/powerpc/powerpc/trap.c >>>=20 >>>=20 >>>=20 >>> # svnlite info /usr/ports/ | grep "Re[plv]" >>> Relative URL: ^/head >>> Repository Root: svn://svn0.us-west.freebsd.org/ports >>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 >>> Revision: 450478 >>> Last Changed Rev: 450478 >>>=20 >>> # svnlite status /usr/ports >>> M /usr/ports/Mk/bsd.port.mk >>> M /usr/ports/Mk/bsd.qt.mk >>> M /usr/ports/audio/liba52/Makefile >>> M /usr/ports/base/gcc/Makefile >>> M /usr/ports/base/gcc/distinfo >>> M /usr/ports/base/gcc/pkg-plist >>> M /usr/ports/devel/libunwind/Makefile >>> ? = /usr/ports/devel/qt5/files/extrapatch-config.tests_unix_arch.test >>> M /usr/ports/lang/gcc7/Makefile >>> M /usr/ports/sysutils/cdrdao/Makefile >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_JavaScriptCore_assembler_ARMA= ssembler.h >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_JavaScriptCore_assembler_ARMv= 7Assembler.h >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_JavaScriptCore_offlineasm_arm= .rb >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_WTF_wtf_Platform.h >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_WebCore_platform_graphics_cpu= _arm_filters_FELightingNEON.cpp >>> ? = /usr/ports/www/qt5-webkit/files/patch-Source_bmalloc_bmalloc_BPlatform.h >>>=20 >>>=20 >>> # more /usr/local/etc/poudriere.d/make.conf >>> WANT_QT_VERBOSE_CONFIGURE=3D1 >>> # >>> DEFAULT_VERSIONS+=3Dperl5=3D5.24 gcc=3D7 >>> # >>> # =46rom a local /usr/ports/Mk/bsd.port.mk extension: >>> ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG=3D >>> # >>> .if ${.CURDIR:M*/devel/llvm*} >>> #WITH_DEBUG=3D >>> .elif ${.CURDIR:M*/www/qt5-webkit*} >>> #WITH_DEBUG=3D >>> .else >>> WITH_DEBUG=3D >>> .endif >>> MALLOC_PRODUCTION=3D >>> # >>> # The system clang for TARGET_ARCH=3Dpowerpc64 >>> # and the system binutils (such as ld) do not >>> # (yet?) mix well. So for ports use the >>> # devel/binutils ones. (A problem before >>> # they are already in place!) >>> #USE_BINUTILS=3D >>> CFLAGS+=3D-B${LOCALBASE}/bin/ >>> CXXFLAGS+=3D-B${LOCALBASE}/bin/ >>> CPPFLAGS+=3D-B${LOCALBASE}/bin/ >>>=20 >>>=20 >>> # svnlite diff /usr/ports/Mk/bsd.port.mk >>> Index: /usr/ports/Mk/bsd.port.mk >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> --- /usr/ports/Mk/bsd.port.mk (revision 450478) >>> +++ /usr/ports/Mk/bsd.port.mk (working copy) >>> @@ -1130,12 +1130,12 @@ >>>=20 >>> # Get the operating system type >>> .if !defined(OPSYS) >>> -OPSYS!=3D ${UNAME} -s >>> +OPSYS!=3D echo FreeBSD >>> .endif >>> _EXPORTED_VARS+=3D OPSYS >>>=20 >>> .if !defined(_OSRELEASE) >>> -_OSRELEASE!=3D ${UNAME} -r >>> +_OSRELEASE!=3D echo 12.0-CURRENT >>> .endif >>> _EXPORTED_VARS+=3D _OSRELEASE >>>=20 >>> @@ -1651,7 +1651,11 @@ >>> STRIP_CMD=3D ${TRUE} >>> .endif >>> DEBUG_FLAGS?=3D -g >>> +.if defined(ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG) >>> +CFLAGS:=3D ${CFLAGS} ${DEBUG_FLAGS} >>> +.else >>> CFLAGS:=3D ${CFLAGS:N-O*:N-fno-strict*} ${DEBUG_FLAGS} >>> +.endif >>> .if defined(INSTALL_TARGET) >>> INSTALL_TARGET:=3D ${INSTALL_TARGET:S/^install-strip$/install/g} >>> .endif >>>=20 >>>=20 >>> (Note: I've had problems with some ${UNAME} use returning empty = strings, >>> which is why I've used echo as a replacement in places. The real = point >>> for the above is the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG use.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Oct 1 09:51:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07C22E3EDF1 for ; Sun, 1 Oct 2017 09:51:49 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A45C47FBD4 for ; Sun, 1 Oct 2017 09:51:48 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:8d79:2312:1fde:a9c1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id B2CCF307C for ; Sun, 1 Oct 2017 09:51:45 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> From: Matthew Seaman Message-ID: Date: Sun, 1 Oct 2017 10:51:39 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="rkOW707fF91exl4CETUWAoO4kcGpAh7tO" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 09:51:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rkOW707fF91exl4CETUWAoO4kcGpAh7tO Content-Type: multipart/mixed; boundary="oDB66cIDb9NR5DeBhK9JiCfvVud3BE2Ms"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: Subject: Re: Status of portupgrade and portmaster? References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> In-Reply-To: --oDB66cIDb9NR5DeBhK9JiCfvVud3BE2Ms Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 30/09/2017 18:06, Kevin Oberman wrote: > John did state that he would continue to support synth. I can't say if = he > has continued to make contributions. In any case, only poudriere is > available for maintaining ports in HEAD and I, for one, feel that it is= > simply unacceptable as it make FreeBSD unusable for those of us with on= ly > "small" systems where the weight poudriere simply can't be justified. (= I > have no system with other than SATA disk drives and, for my current nee= ds, > 1 TB of SATA on my development system and .5TB on my production system = is > adequate. Both systems are physically constrained in expansion capabili= ty, > though otherwise easily meet my requirements. I don't know what it is about poudriere that elicits this immediate reaction that it is some sort of behemoth, trampling through disks by the bushel, shouldering aside other processes to seize the best bits of RAM and making CPUs cry with incessant demands for more cycles. It's simply not so. poudriere is really a very thin layer of shell scripts (and a few other bits) over the general ports make system. All of the really heavy lifting is done by the compilers and so forth /that you'ld have to invoke anyhow/. In fact, I'd say that if your system is /at all/ capable of building the ports you want, then it is perfectly capable of running poudriere to help automate that. Yes, the pkg builders used by the project are pretty chunky bits of kit. That's because they are building some 30,000 ports for about 8 different combinations of OS and CPU architecture with a cycle time of less than two days. If you're just building a few hundred ports for your own consumption, then you don't need anything like that amount of resource. I manage perfectly well with a 6-year old Core2Duo with 8GB RAM and some 500GB SSDs which cost me under =C2=A3500 originally + about =C2=A3200 for repla= cement drives later on. Which also runs a bunch of other stuff including my mail system. Cheers, Matthew --oDB66cIDb9NR5DeBhK9JiCfvVud3BE2Ms-- --rkOW707fF91exl4CETUWAoO4kcGpAh7tO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ0LqxXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAThX4P/i/B1cUVFdV1ntEFb6NiPLae CXr3nsWS3V6nzD5W5aqRFLlkaLrHftY+LmqdPErZ6GOhG2AQB8oTKiZ9gXreDTmn WfccDdX7ltmiVsqLWgL1YytBxlSwIvqPuAjvqbXF8OzKuWyiz4J0jZnA2rVTciXv 9qO5zw5yrT3V6/CZa5XwC3ZawLnp4TNcEhQRQl8odh/XriVfOKkZgbjaErpF09iZ D0jAnCzvMq0SSrB7SfhGLzukt5fyQq+UL+l+uPk4TSaoTYSgs1f7bB9xLT+tK62A Q5zORGC1nCHilc4NC+6oVcdh9jvub/QglIWqZCXQJU1E7tpYPpF8TSt+idk9ZyBA V2wG1RLCCDx0NP/ghw8SZiGwclyOBTTs6WuhlEvXkf9mwjjiQyls/PDeMxK/u/JL d8XFkoqktxZ11zvAtRILsVBC2oTq5+SO677Oguvb/EgslaSYWCZnB8s1qtNTKvZ9 DILxG9ycWbDPp2Svw9wx1wQKpEWJeBIZ/fJr+RuF824w3fycTdLDh8hZbmLqlPsX //GCinUvx6PHyL1i5s7D0Bv0nYkkTu8H/UdJyzelyGQkMjKvznjymVxNoc8iVarC t+5uEN+w3GDItE8/9etnfE2bthZJq4mwtsk9oNU4Uepkmt/gMYSIti0iEDxvbb7a ChD6nOCbp8EXQgH2wSJJ =JkSw -----END PGP SIGNATURE----- --rkOW707fF91exl4CETUWAoO4kcGpAh7tO-- From owner-freebsd-ports@freebsd.org Sun Oct 1 09:20:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15925E3C690 for ; Sun, 1 Oct 2017 09:20:49 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta02.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ED9AF7EBCD for ; Sun, 1 Oct 2017 09:20:48 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([74.134.208.22]) by cmsmtp with ESMTP id yaQYd8ene3BLhyaQadORQ0; Sun, 01 Oct 2017 09:20:48 +0000 Date: Sun, 01 Oct 2017 09:19:56 +0000 From: "Thomas Mueller" To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com>, <20171001041404.GD27224@lonesome.com> Subject: Re: Status of portupgrade and portmaster? X-CMAE-Envelope: MS4wfN47gb0vlQEkUdp+KIau5W6TmqLGPQUB/bFEZgIaVaF7RZ5V7U8RjSs67sfPZHBK8lvoxgJfSvIR4E33mo9VlnlQgxlyHdzmsVlvQF7mGlCtdqJNw0nh HHjeTOFbYlbaQLYCBEMm/zhZ6RNYt3CNxXgikWtE6o5wxUqjdT5qvhDd X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 09:20:49 -0000 > John did state that he would continue to support synth. I can't say if he > has continued to make contributions. In any case, only poudriere is > available for maintaining ports in HEAD and I, for one, feel that it is > simply unacceptable as it make FreeBSD unusable for those of us with only > "small" systems where the weight poudriere simply can't be justified. (I > have no system with other than SATA disk drives and, for my current needs, > 1 TB of SATA on my development system and .5TB on my production system is > adequate. Both systems are physically constrained in expansion capability, > though otherwise easily meet my requirements. > As a result, I am no longer able to track HEAD and, if the issue is not > resolved in some manner before 11 support ends, will be forced to move from > FreeBSD after an using it for over 2 decades. I certainly hope that this is > not what happens. > Kevin Oberman, Part time kid herder and retired Network Engineer I keep svn-updating 11-STABLE and HEAD, but the ino64 issue with some ports including gcc(5,6)-aux holds me back from activity on HEAD. But conceivably there could be a fix in the future. I also keep cvs-updating NetBSD-HEAD and pkgsrc. On FreeBSD, I am also miffed by the lack of support for my Realtek 8111E/8168 chip on MSI Z77 MPOWER motherboard, especially after that Ethernet worked for a time, and still does for Linux (System Rescue CD) and NetBSD. Synth and pkgng in pkgsrc seem to be falling into desuetude; gcc6-aux is broken for NetBSD (stated in the Makefile). I wonder also about the status of synth and possibly poudriere on DragonFlyBSD, idly curious in that I am more favorably impressed by Linux or Haiku, compared to DragonFlyBSD. Tom From owner-freebsd-ports@freebsd.org Sun Oct 1 10:26:37 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F415E0F5F1 for ; Sun, 1 Oct 2017 10:26:37 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (mx.irealone.hr [IPv6:2a01:4f8:212:2d90::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42FBD81078 for ; Sun, 1 Oct 2017 10:26:36 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id B25DBAEBC; Sun, 1 Oct 2017 12:26:25 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 419AEAEB8 for ; Sun, 1 Oct 2017 12:26:25 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 01 Oct 2017 12:26:25 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> Message-ID: <5813dd8ee208549f2a96672723d47532@acheronmedia.com> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 10:26:37 -0000 On 2017-10-01 11:51, Matthew Seaman wrote: > poudriere is really a very thin layer of shell scripts (and a few other > bits) over the general ports make system. All of the really heavy > lifting is done by the compilers and so forth /that you'ld have to > invoke anyhow/. There is one tiny problem that users see often and that's the rebuilding of all reverse deps for any port that changed, which can result with frequent rebuilds of tens or hundreds of packages. But -- that's only a good thing. I've never had issues with eg. perl upgrades that portmaster users seem to have often. However, CCACHE is very effective in this situation. As an example CCACHE reduces building of Firefox from ~45 minutes down to 3-4 minutes, in my case. Another problem is poudriere's inability to reuse already installed packages, if they're a dependency for something being built by it. Personally I'd never use that option, as I want clean, isolated rebuilds of everything affected, but I can understand how quick building of one or two packages could use already installed deps, if people wanted that (and break any promise of integrity facilitated with isolated builds). I'll also second the opinion -- if you're building from ports on a machine anyway, poudriere does not in any way require any more resources except to store produced packages and ccache files, which is not much. -- Vlad K. From owner-freebsd-ports@freebsd.org Sun Oct 1 10:34:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6AFBAE0F916 for ; Sun, 1 Oct 2017 10:34:18 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-oln040092004066.outbound.protection.outlook.com [40.92.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC9481414 for ; Sun, 1 Oct 2017 10:34:17 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=f7P5zR2JJRx4Pn7b9TCRad9f7imwemo4G7AMFY4EBNI=; b=f4y+wlfp0l/7c4FYifB/HcnE5zpUGeumKp8LjB4onyE9X9dg5uMzmrA1HFWvwx89hGMG09Srp3STdPSExmNXNkn3Yd5qLUt4hQwh7bQSWoNqxUBrPojbq8i87M6Gi7LJbJhYzhzWU8dApiC1PekfBHUqVdFWIYR6LTwr3q9pE2tLYxDspYLIr51dFhGd0Lb2PsfwhKY6OqLvx4XYKt/ddq8VTW9ZTMx2QA0LPmGDN19BrZT87BMnbm3c2bd++2yMz68d9cEoHg26aGrE8fhu7or3c34cQVdz3iy8eQunTCoIc8epfXOlYkJMs+ssTYAVRE5Iq7Ya4R6CtaIb3m9wkQ== Received: from BL2NAM02FT055.eop-nam02.prod.protection.outlook.com (10.152.76.58) by BL2NAM02HT217.eop-nam02.prod.protection.outlook.com (10.152.77.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.56.11; Sun, 1 Oct 2017 10:34:16 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.76.59) by BL2NAM02FT055.mail.protection.outlook.com (10.152.77.126) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.56.11 via Frontend Transport; Sun, 1 Oct 2017 10:34:16 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.20.0077.016; Sun, 1 Oct 2017 10:34:16 +0000 From: Carmel NY To: FreeBSD Subject: Re: Status of portupgrade and portmaster? Thread-Topic: Status of portupgrade and portmaster? Thread-Index: AQHTOQa5V6RAlsDMdkWBuhE2Y+Zwrw== Date: Sun, 1 Oct 2017 10:34:16 +0000 Message-ID: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> In-Reply-To: Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:40A55ED3A801B7BABF8BB0B68B1580C7510A7205D85FE0BC16D6CF049A00E8A2; UpperCasedChecksum:9432625C58F0B62D7AE7880D89DE06E22912CCB052B2EBB9326CF496C2435D34; SizeAsReceived:7580; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [wJ8GLuSUWMqIDGrmJ2UoIPoIY1bAR/eU] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BL2NAM02HT217; 6:XTJSsEtVUzabHMNN7uXsBKc+skz7lRX64YXxcWSFPOSXH1TZGwLHCq0kUF8RQGq62EgQoCTUl5t94Ic3wXH4pyKRh05JNHXYhbRw3CbFp5ghjFMH+fU5/rjSaZQdExSk3ztiF/WQa5WBrSrGxG314HIjA81ndbtwVaguQyzdEbxnDNNgOq7ckkg08Yv8IxmUfkOpGrvHmI+RgiNqDQgWFG3hnPpum+8qBo0c6IrO4Pb+oUjW7u8DbzAEK87gPjBSXgh8Qw9KZea1UIXiWJIyWg2tfcycokbCi89pBSQj8yw/x/Z4gW5FinotPypEnrjERKf+9bHyIPEO7nTlXRGjXQ==; 5:A+2OQZAA6CceHFAcWsIrm3ziDRTtkcWj3o9EX+I4uxCgmF9RfJBnjK4VL2sVBfzxZiIXMt40E04efwSyQenp1WW8dvBHRHfV+q4L7JG4a+eUcNV0bWq/w5asHyn8Ssa4VhjCnMTwwGBNDsx6VCgaCg==; 24:ymHukkGnxw6iqiqgA/nebY2f9o4yxCw9uoMMSOye6jTdhOrGN4IBX8qZtdeUpZWb7Vw7i77H4vEnbzbtOwqBYk5fBSNOQ62Wt/5ep310As8=; 7:a32qyG3J8FtFJjbpoUCEcKgpZ/7xdsK57vZdJ7jjRORF8nMNTFtCXs7yT4DjsZbYTTfmiOnYG/m58qQwBbGZw/QmPzKbw+kA/Ok4m3YULMh7oPyblNkwzwhqTCTui+eHCtgoE9CIPnhbjASaiLz96N7UWscm2b2aCK4S2qB+vDswvaieW7yZRG86Ok8Hspp4D74ItSNOf5NI0B8c+/Qmn9f10iL8V12JTqejaJuACY4= x-incomingheadercount: 47 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: a16f2525-39ec-46e2-e031-08d508b7f6ad x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:BL2NAM02HT217; x-ms-traffictypediagnostic: BL2NAM02HT217: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:BL2NAM02HT217; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BL2NAM02HT217; x-forefront-prvs: 0447DB1C71 x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BL2NAM02HT217; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <7CD5D1EC3CDD8A45977DC8147C76D1F5@namprd20.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2017 10:34:16.2014 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT217 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 10:34:18 -0000 T24gU3VuLCAxIE9jdCAyMDE3IDEwOjUxOjM5ICswMTAwLCBNYXR0aGV3IFNlYW1hbiBzdGF0ZWQ6 DQoNCj5PbiAzMC8wOS8yMDE3IDE4OjA2LCBLZXZpbiBPYmVybWFuIHdyb3RlOg0KPj4gSm9obiBk aWQgc3RhdGUgdGhhdCBoZSB3b3VsZCBjb250aW51ZSB0byBzdXBwb3J0IHN5bnRoLiBJIGNhbid0 IHNheSBpZiBoZQ0KPj4gaGFzIGNvbnRpbnVlZCB0byBtYWtlIGNvbnRyaWJ1dGlvbnMuIEluIGFu eSBjYXNlLCBvbmx5IHBvdWRyaWVyZSBpcw0KPj4gYXZhaWxhYmxlIGZvciBtYWludGFpbmluZyBw b3J0cyBpbiBIRUFEIGFuZCBJLCBmb3Igb25lLCBmZWVsIHRoYXQgaXQgaXMNCj4+IHNpbXBseSB1 bmFjY2VwdGFibGUgYXMgaXQgbWFrZSBGcmVlQlNEIHVudXNhYmxlIGZvciB0aG9zZSBvZiB1cyB3 aXRoIG9ubHkNCj4+ICJzbWFsbCIgc3lzdGVtcyB3aGVyZSB0aGUgd2VpZ2h0IHBvdWRyaWVyZSBz aW1wbHkgY2FuJ3QgYmUganVzdGlmaWVkLiAoSQ0KPj4gaGF2ZSBubyBzeXN0ZW0gd2l0aCBvdGhl ciB0aGFuIFNBVEEgZGlzayBkcml2ZXMgYW5kLCBmb3IgbXkgY3VycmVudCBuZWVkcywNCj4+IDEg VEIgb2YgU0FUQSBvbiBteSBkZXZlbG9wbWVudCBzeXN0ZW0gYW5kIC41VEIgb24gbXkgcHJvZHVj dGlvbiBzeXN0ZW0gaXMNCj4+IGFkZXF1YXRlLiBCb3RoIHN5c3RlbXMgYXJlIHBoeXNpY2FsbHkg Y29uc3RyYWluZWQgaW4gZXhwYW5zaW9uIGNhcGFiaWxpdHksDQo+PiB0aG91Z2ggb3RoZXJ3aXNl IGVhc2lseSBtZWV0IG15IHJlcXVpcmVtZW50cy4gIA0KPg0KPkkgZG9uJ3Qga25vdyB3aGF0IGl0 IGlzIGFib3V0IHBvdWRyaWVyZSB0aGF0IGVsaWNpdHMgdGhpcyBpbW1lZGlhdGUNCj5yZWFjdGlv biB0aGF0IGl0IGlzIHNvbWUgc29ydCBvZiBiZWhlbW90aCwgdHJhbXBsaW5nIHRocm91Z2ggZGlz a3MgYnkNCj50aGUgYnVzaGVsLCBzaG91bGRlcmluZyBhc2lkZSBvdGhlciBwcm9jZXNzZXMgdG8g c2VpemUgdGhlIGJlc3QgYml0cyBvZg0KPlJBTSBhbmQgbWFraW5nIENQVXMgY3J5IHdpdGggaW5j ZXNzYW50IGRlbWFuZHMgZm9yIG1vcmUgY3ljbGVzLg0KPg0KPkl0J3Mgc2ltcGx5IG5vdCBzby4N Cj4NCj5wb3VkcmllcmUgaXMgcmVhbGx5IGEgdmVyeSB0aGluIGxheWVyIG9mIHNoZWxsIHNjcmlw dHMgKGFuZCBhIGZldyBvdGhlcg0KPmJpdHMpIG92ZXIgdGhlIGdlbmVyYWwgcG9ydHMgbWFrZSBz eXN0ZW0uICBBbGwgb2YgdGhlIHJlYWxseSBoZWF2eQ0KPmxpZnRpbmcgaXMgZG9uZSBieSB0aGUg Y29tcGlsZXJzIGFuZCBzbyBmb3J0aCAvdGhhdCB5b3UnbGQgaGF2ZSB0bw0KPmludm9rZSBhbnlo b3cvLg0KPg0KPkluIGZhY3QsIEknZCBzYXkgdGhhdCBpZiB5b3VyIHN5c3RlbSBpcyAvYXQgYWxs LyBjYXBhYmxlIG9mIGJ1aWxkaW5nIHRoZQ0KPnBvcnRzIHlvdSB3YW50LCB0aGVuIGl0IGlzIHBl cmZlY3RseSBjYXBhYmxlIG9mIHJ1bm5pbmcgcG91ZHJpZXJlIHRvDQo+aGVscCBhdXRvbWF0ZSB0 aGF0Lg0KPg0KPlllcywgdGhlIHBrZyBidWlsZGVycyB1c2VkIGJ5IHRoZSBwcm9qZWN0IGFyZSBw cmV0dHkgY2h1bmt5IGJpdHMgb2Yga2l0Lg0KPiBUaGF0J3MgYmVjYXVzZSB0aGV5IGFyZSBidWls ZGluZyBzb21lIDMwLDAwMCBwb3J0cyBmb3IgYWJvdXQgOA0KPmRpZmZlcmVudCBjb21iaW5hdGlv bnMgb2YgT1MgYW5kIENQVSBhcmNoaXRlY3R1cmUgd2l0aCBhIGN5Y2xlIHRpbWUgb2YNCj5sZXNz IHRoYW4gdHdvIGRheXMuDQo+DQo+SWYgeW91J3JlIGp1c3QgYnVpbGRpbmcgYSBmZXcgaHVuZHJl ZCBwb3J0cyBmb3IgeW91ciBvd24gY29uc3VtcHRpb24sDQo+dGhlbiB5b3UgZG9uJ3QgbmVlZCBh bnl0aGluZyBsaWtlIHRoYXQgYW1vdW50IG9mIHJlc291cmNlLiAgSSBtYW5hZ2UNCj5wZXJmZWN0 bHkgd2VsbCB3aXRoIGEgNi15ZWFyIG9sZCBDb3JlMkR1byB3aXRoIDhHQiBSQU0gYW5kIHNvbWUg NTAwR0INCj5TU0RzIHdoaWNoIGNvc3QgbWUgdW5kZXIgwqM1MDAgb3JpZ2luYWxseSArIGFib3V0 IMKjMjAwIGZvciByZXBsYWNlbWVudA0KPmRyaXZlcyBsYXRlciBvbi4gIFdoaWNoIGFsc28gcnVu cyBhIGJ1bmNoIG9mIG90aGVyIHN0dWZmIGluY2x1ZGluZyBteQ0KPm1haWwgc3lzdGVtLg0KDQpU aGlzIGlzIHByb2JhYmx5IE9UIGZvciB0aGlzIHRocmVhZDsgaG93ZXZlciwgYXQgdGhpcyBwb2lu dCBJIGRvbuKAmXQgdGhpbmsgaXQNCm1hdHRlcnMgbXVjaC4NCg0KSSBoYXZlIHJlYWQgdXAgb24g cG91ZHJpZXJlIGFsdGhvdWdoIEkgaGF2ZSBuZXZlciB1c2VkIGl0LiBJIGhhdmUgc2V2ZXJhbA0K cXVlc3Rpb25zIHRoYXQgSSBjYW5ub3QgZmluZCB0aGUgYW5zd2VyIHRvby4NCg0KMS4gRG9lcyBp dCBkZXRlcm1pbmUgb3V0LW9mLWRhdGUgdXBkYXRlIHBhY2thZ2VzIGF1dG9tYXRpY2FsbHkgb3Ig ZG9lcw0KdGhlIHVzZXIgaGF2ZSB0byBkZXRlcm1pbmUgdGhhdCB3aGF0IGlzIG91dC1vZi1kYXRl IGFuZCBmZWVkIHRoZW0gdG8gcG91ZHJpZXJlDQptYW51YWxseSBhbmQgaW4gdGhlIHByb3BlciBv cmRlcj8NCg0KMi4gRnJvbSB3aGF0IEkgaGF2ZSByZWFkLCB0aGUgdXNlciBpcyByZXF1aXJlZCB0 byBpbnN0YWxsIGVhY2ggcGFja2FnZQ0KbWFudWFsbHkuIElzIHRoYXQgY29ycmVjdD8NCg0KSSBo YXZlIGEgc21hbGwgc3lzdGVtLiBUaHJlZSBQQ3MgcGx1cyBhIG51bWJlciBvZiBsYXB0b3BzLiBP bmx5IG9uZSBtYWNoaW5lDQpydW5zIEZyZWVCU0QuIEkgZG9u4oCZdCBoYXZlIHRoZSB0aW1lIHRv IGJlIGEgc2xhdmUgdG8gdGhpcyBzeXN0ZW0uIEl0IGFwcGVhcnMNCnRoYXQgdGhlcmUgaXMgYSBj b25zaWRlcmFibGUgYW1vdW50IG9mIG1hbnVhbCBjb25maWd1cmF0aW9uIHRvIGdldCBwb3Vkcmll cmUNCnVwIGFuZCBydW5uaW5nLCB3aGljaCBtZWFucyB0aGVyZSBpcyBhIHNpZ25pZmljYW50IHBv c3NpYmlsaXR5IG9mIG1ha2luZw0KbWlzdGFrZXMuDQoNClN5bnRoLCBhbmQgYmVmb3JlIHRoYXQg 4oCccG9ydG1hbmFnZXLigJ0sIGFuZCB0aGVuIOKAnHBvcnR1cGdyYWRl4oCdIGRvIGFsbCB0aGUg aGVhdnkNCmxpZnRpbmcgbGVhdmluZyBtZSBmcmVlIHRvIHdvcmsgb24gbW9yZSBpbXBvcnRhbnQg cHJvamVjdHMuIEkgc3VwcG9zZSBJIGNvdWxkDQphbHdheXMgZ28gYmFjayB0byDigJxwb3J0dXBn cmFkZeKAnTsgaG93ZXZlciwgSSB1bmRlcnN0YW5kIHRoYXQgaXQgaXMgbm90IGJlaW5nDQptYWlu dGFpbmVkIGVpdGhlci4NCg0KSWYgRnJlZUJTRCBjYW5ub3QgZ2V0IHRoZSBwcm9ibGVtcyB3aXRo IHN5bnRoIGNvcnJlY3RlZCB3aGVuIEZyZWVCU0QtMTIgaXMNCnJlbGVhc2VkLCBwZXJoYXBzIGl0 IHdpbGwgYmUgdGltZSB0byBjb25zaWRlciBhIG5ldyBPUy4NCg0KLS0gDQpDYXJtZWwNCg== From owner-freebsd-ports@freebsd.org Sun Oct 1 10:49:12 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95F60E0FC89 for ; Sun, 1 Oct 2017 10:49:12 +0000 (UTC) (envelope-from vlad@acheronmedia.hr) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3577A81840 for ; Sun, 1 Oct 2017 10:49:11 +0000 (UTC) (envelope-from vlad@acheronmedia.hr) Received: by mx.irealone.hr (Postfix, from userid 58) id F1F3EAEE2; Sun, 1 Oct 2017 12:49:08 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id B5E0CAEDE for ; Sun, 1 Oct 2017 12:49:07 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 01 Oct 2017 12:49:07 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> Message-ID: <5b799f770a1c605a49dc025e1498be62@acheronmedia.hr> X-Sender: vlad@acheronmedia.hr User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 10:49:12 -0000 On 2017-10-01 12:34, Carmel NY wrote: > > 1. Does it determine out-of-date update packages automatically or does > the user have to determine that what is out-of-date and feed them to > poudriere > manually and in the proper order? > > 2. From what I have read, the user is required to install each package > manually. Is that correct? It's not. Poudriere builds a pkg repo, and automatically rebuilds all ports that have changed version (including epoch and portrevision, so essentially -- changed version string), including all ports that depend on ports that changed (see my previous post about frequent rebuilds), or became a new dependency. So you can have it build updates in the background and when you're done, just issue pkg upgrade. Another benefit of this approach is that you don't get partial updates for a program that's in active use. I've seen this cause failure a lot of times, eg with perl. The master program is running or being actively run (from cron or initiated by user), not yet updated but a dep just updated. Crash. > I have a small system. Three PCs plus a number of laptops. Only one > machine > runs FreeBSD. I don’t have the time to be a slave to this system. It > appears > that there is a considerable amount of manual configuration to get > poudriere > up and running, which means there is a significant possibility of > making > mistakes. Depends on the definition of "significant". With poudriere you really have four steps at minimum to get started: 1. create the builder jail (poudriere jail -c ...) 2. create the ports tree (poudriere ports -c ...) -- create new, or point it to use system's /usr/ports 3. create a file that lists ports you want build for that repo 3a. optional step, issue poudriere options ..., to set non-default options . 4. configure /etc/pkg.conf to use the repo poudriere is building After that, the workflow is simple: 1. update ports tree (poudriere ports -u) 2. manage new/changed options (poudriere options ...) 3. run build (poudriere bulk ...) 4. when it's done, pkg upgrade It's covered in the handbook: https://www.freebsd.org/doc/handbook/ports-poudriere.html The above is just a minimum, but poudriere allows you to have many builder jails (eg for 64 or 32 bit, for different ABIs, ...), and many package option sets, so essentially it can create many repositories that differ in supported arch, abi, options used, packages listed, ... -- Vlad K. Acheron Media, Croatia www.acheronmedia.hr +385 95 536 3850 From owner-freebsd-ports@freebsd.org Sun Oct 1 16:24:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D0FEE287E3 for ; Sun, 1 Oct 2017 16:24:43 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 730DF6547F for ; Sun, 1 Oct 2017 16:24:43 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6F326E287E2; Sun, 1 Oct 2017 16:24:43 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E9AEE287E1 for ; Sun, 1 Oct 2017 16:24:43 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05FD56547E for ; Sun, 1 Oct 2017 16:24:42 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x243.google.com with SMTP id k4so4423904wmc.1 for ; Sun, 01 Oct 2017 09:24:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=MUZ19afMhtV67yeGksZmtPv0qVVmTUhPj43yIzJruhQ=; b=Iw1F8sPPBcKQ6dRPvkuKAd4Z7CXIcoExwGfDBkq+h/qua+or/rnfZvd4VlQd0lcCQB +zTaO5EKo6LjJsHZ2cHMZtl7jjklf0xfcMHom8YD1VKShJPvkJwMHlvQYX2OAriXahwB LPZcuQmtnkHoWHAA9S23ixmU/f1gA0hbUjluW47chon62O3RQKb1XCWC4WhOjx4v5U5h K7uSx93ueIVUXZj2+sa5OuNWDyUoWZ6Lm1n7Xm4xJqRr/N6W5CWmR4Yde5S8OLfs+Uqh /9z6yD/WVnUm7XqJv7B3x9dNelkhiQ0z3rKoKepoSh9eeWvdUGLUIkIPBA5gbFObDE+F hmrQ== X-Gm-Message-State: AHPjjUhjHHfvFinmWhUvPVwoavQNPOQBfGeKzu6XftxG/kIayWcEusnJ J4LKAd+iyMXcdxJnAvOTXqk7HA== X-Google-Smtp-Source: AOwi7QBumCGqR2EhDtObMXw6MLbTPlkTAKmRMf4S8PLUfBPQdTISN7pCRR/awTocQ+g945pK66lZ6A== X-Received: by 10.28.163.198 with SMTP id m189mr8056782wme.76.1506875081198; Sun, 01 Oct 2017 09:24:41 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id d18sm3140412wra.89.2017.10.01.09.24.39 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 01 Oct 2017 09:24:40 -0700 (PDT) Date: Sun, 1 Oct 2017 17:24:37 +0100 From: RW To: ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171001172437.32f4a2c1@gumby.homeunix.com> In-Reply-To: <5813dd8ee208549f2a96672723d47532@acheronmedia.com> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <5813dd8ee208549f2a96672723d47532@acheronmedia.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 16:24:43 -0000 On Sun, 01 Oct 2017 12:26:25 +0200 Vlad K. wrote: > Another problem is poudriere's inability to reuse already installed > packages, if they're a dependency for something being built by it. > Personally I'd never use that option, as I want clean, isolated > rebuilds of everything affected, but I can understand how quick > building of one or two packages could use already installed deps, if > people wanted that (and break any promise of integrity facilitated > with isolated builds). Do you mean as opposed to installing the dependencies from the repository, or are you saying that it rebuilds them? From owner-freebsd-ports@freebsd.org Sun Oct 1 17:24:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1A5AE2A2C2 for ; Sun, 1 Oct 2017 17:24:53 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 430916807D for ; Sun, 1 Oct 2017 17:24:53 +0000 (UTC) (envelope-from tingox@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id d10so1498645lfg.11 for ; Sun, 01 Oct 2017 10:24:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=jdUb6yKSx7DpXCbOnTAeCme64JtlkiGS3HStwnimJAs=; b=DTHhY5onXFFX5YwkRwCpyIOzgKtWYJeD6AMS3Cx9nzFW3sQCgmmyaF/xtem6tKCSrT qutslwvli0k03lnne9WNIzJSCAjAz1rf2IFS+Exu3g4h6yWY3uhvHs1kWtdyOAC5rCYq d1hsd+Y9WghdHSMwcfh/sUzvL+eFuMVMazEOfxRtZgphb3ynmi4p5ShwOEYAagywf87u RSMGv6A7ImNYwztIFlKP3IFIqtjdX0+cfXqUWqajxsuUIhp3jc3LZbLI6OxebtveDqzo FqwZXc8IGtP7xgBb5UpPJVuvLmCJ5KNcDn9CTPbY3u+xwsOUUDl0G41QGYGxHgEuYocp vlkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=jdUb6yKSx7DpXCbOnTAeCme64JtlkiGS3HStwnimJAs=; b=WyfgKLz3L1yq/QdRMXPO1836VGdiektkBGfXOrg2fZXNlYow81A9v7g4N1ZC0SVzJI N8tok2as+CxLHXUEhfuE74yzlLYMyzgecxpRztE43/E1dhguUo2nUikFiu3XKSs2CIpb qF6VuvIusURaGoSxcIvy2ThXL/S2stmzWbfWGuDgeqKoAgAU5+fbOi9bCx4Gh8sXn6FQ dYa6DlTnz/INIzrLmpzr0ePqmC1001JpRES37METd3sOnQG4kjtJWj09T3BnWBLwUWIP cVqIw/Tv4u7wfKCK/vKV8hsMpqgp/YlPU40xBSlx9c7HO0VEOofVfK1lMDLA1ajpGufK OkjQ== X-Gm-Message-State: AMCzsaUByXfk5HWMbcX814Gg3cCRPjrNGVblBqs5H2AXZkrM837R1p6x j97g2iyzic2BFL7eUwhedqT78tsegHpTeFNAi6w= X-Google-Smtp-Source: AOwi7QCBvS/9oAGaabRV7sztqm4u7AV7+tEO3oesXU7XgmhuuYXHurdeuuHMOaQara3yi7EIpvOVCOdOGPWkLIF6xbo= X-Received: by 10.25.141.196 with SMTP id p187mr3037874lfd.137.1506878691355; Sun, 01 Oct 2017 10:24:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.18.36 with HTTP; Sun, 1 Oct 2017 10:24:50 -0700 (PDT) In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> From: Torfinn Ingolfsen Date: Sun, 1 Oct 2017 19:24:50 +0200 Message-ID: Subject: Re: Status of portupgrade and portmaster? To: FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 17:24:53 -0000 On Sun, Oct 1, 2017 at 12:34 PM, Carmel NY wrote: > lifting leaving me free to work on more important projects. I suppose I c= ould > always go back to =E2=80=9Cportupgrade=E2=80=9D; however, I understand th= at it is not being > maintained either. FWIW, portupgrade has received enough maintenance that it continues to work nicely on at least stable/11 and stable/10. And I am grateful for that. HTH --=20 Regards, Torfinn Ingolfsen From owner-freebsd-ports@freebsd.org Sun Oct 1 17:29:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82D99E2A513 for ; Sun, 1 Oct 2017 17:29:28 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5F415683A7 for ; Sun, 1 Oct 2017 17:29:28 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: by mailman.ysv.freebsd.org (Postfix) id 5B8B7E2A512; Sun, 1 Oct 2017 17:29:28 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B1C3E2A511 for ; Sun, 1 Oct 2017 17:29:28 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C76C683A4 for ; Sun, 1 Oct 2017 17:29:27 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: by mail-wr0-x242.google.com with SMTP id k10so2393455wrk.3 for ; Sun, 01 Oct 2017 10:29:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=phpandmore-net.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=oXF+roDP8ZPRaamXAILGfwCUEddiuuiXNqFfjcyT6mk=; b=fWmov5n3Er8Rx6Ff1FbV+pBlvqWGAXOrgwN5+2Q6aCA8MM4Do0o5rIsPGhYY1mQ7nQ tKXw9hhtQh/SySZ75bIXUhRpCF3Y/KPF+/hQqKSDP31isSMtMgyJpQKpaM5wdxKbKHRw Lvr8nHqzyCiGtt/jA3Slr1n34/v9/eEES6Bsw9jQB1u1aHtOeYE3PMyX5idt5MfQe6JW WhJDx/Pqr15rxYBIvjSBmwiQSr5D7vWp1abec7cEBA7i6SncLRUSm/E670AnyMSJFtWs TdqhFudtM6tKz2xYTtKSNaXYl6F1Xgy5BRYJZl1Hou3Z0twyWoIH9EXLo9olh3dwu1fe dv+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=oXF+roDP8ZPRaamXAILGfwCUEddiuuiXNqFfjcyT6mk=; b=kXycHd90iHx/MBi4JqbIz60BH85ccLYolFDDm251ADwG3O+1IUQZDGjlE5Tf2Ki0Og 70sI1hXncljuG5+Kw0oMroiY/CPuaqpXaZ+c6MAbcXoW/fEiplxV5YcEyNmkgvrXP7zU b5WZ5G/MVi+cCTUEXbOHtYWS8tifYBnGnLAqR/dNptMfpFjtJv/t820EMIpS9zqov3+P SYGzK4dbPqZGDcs/3fqAYlkoSLSrw4Xg7r18c2cy2zURAzl+QupaoZeRNBUjymPnFXPb y8ymDhQ5kRi3TaLjiazNm6w2Qi1+epEcZp5prg6Stcc+WlOW4RMmc3qIZziMe+6S+w4s dtNg== X-Gm-Message-State: AMCzsaWvGAdbczifaTq0oYzWhABxXFI4ZvqUZDwC6UbBkzsdr4jhVOct plm9wLHfh3+yNhQz6pVPKZYd/ADLPgo= X-Google-Smtp-Source: AOwi7QAtdu7n9k6jvbeE4y2wL6eyviajfwMbXwbdh4r/TCsKJTErE/Lg2BN2X1v9Lyg9DXmCD6qUKQ== X-Received: by 10.223.173.234 with SMTP id w97mr337833wrc.26.1506878966301; Sun, 01 Oct 2017 10:29:26 -0700 (PDT) Received: from [10.0.0.1] ([94.230.86.101]) by smtp.gmail.com with ESMTPSA id 92sm989005wrd.15.2017.10.01.10.29.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Oct 2017 10:29:25 -0700 (PDT) To: "ports@freebsd.org" From: Amit Yaron Subject: Debugging A Port Message-ID: Date: Sun, 1 Oct 2017 20:29:23 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 17:29:28 -0000 Hi, What action will make the Make command to recompile a source file? Thanks, Amit From owner-freebsd-ports@freebsd.org Sun Oct 1 17:42:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2814AE2A979 for ; Sun, 1 Oct 2017 17:42:56 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 172C6689AD for ; Sun, 1 Oct 2017 17:42:56 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 166B5E2A978; Sun, 1 Oct 2017 17:42:56 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16007E2A976 for ; Sun, 1 Oct 2017 17:42:56 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D25D0689AC for ; Sun, 1 Oct 2017 17:42:55 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dyiGW-000OM4-H0; Sun, 01 Oct 2017 19:42:56 +0200 Date: Sun, 1 Oct 2017 19:42:56 +0200 From: Kurt Jaeger To: Amit Yaron Cc: "ports@freebsd.org" Subject: Re: Debugging A Port Message-ID: <20171001174256.GI86601@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 17:42:56 -0000 Hi! > What action will make the Make command to recompile a source file? That depends on the port, there's no generic way to say. Basically, the port framework adds a wrapper of targets around the upstream source Makefile and those targets can shield a recompile from happening. What sometimes work is this: cd work// make -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Sun Oct 1 18:25:33 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BE9FE2B962 for ; Sun, 1 Oct 2017 18:25:33 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CD9DB6A244 for ; Sun, 1 Oct 2017 18:25:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 17697 invoked from network); 1 Oct 2017 18:25:30 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 1 Oct 2017 18:25:30 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sun, 01 Oct 2017 14:25:30 -0400 (EDT) Received: (qmail 8009 invoked from network); 1 Oct 2017 18:25:30 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 1 Oct 2017 18:25:30 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 21C90EC9390; Sun, 1 Oct 2017 11:25:30 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: lang/pdflib: I've submitted bugzilla 222722 with a patch for allowing lang/pdflib to build under __POWERPC__ Message-Id: <0B97D367-F22F-43A9-BF96-A684B2C40ECA@dsl-only.net> Date: Sun, 1 Oct 2017 11:25:29 -0700 To: FreeBSD PowerPC ML , FreeBSD Ports X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 18:25:33 -0000 I wrote in bugziila 222722: > [I tried to build math/gnuplot and it was > indirectly blocked by print/pdflib failing > to build for "missing" include files.] > > The following avoids print/pdflib classifying the > context as an old MAC context (pre-MACOSX) when > building for powerpc64 (for example): > > # more /usr/ports/print/pdflib/files/patch-libs_pdcore_pc__config.h > --- libs/pdcore/pc_config.h.orig 2012-06-06 11:58:58 UTC > +++ libs/pdcore/pc_config.h > @@ -179,9 +179,11 @@ > > /* try to identify Mac OS 9 compilers */ > > +#if 0 > #if (defined macintosh || defined __POWERPC__ || defined __CFM68K__) && \ > !defined MAC && !defined MACOSX && !defined __BEOS__ > #define MAC > +#endif > #endif > > /* === Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Oct 1 18:36:05 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10267E2BBE2 for ; Sun, 1 Oct 2017 18:36:05 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD696A60B for ; Sun, 1 Oct 2017 18:36:04 +0000 (UTC) (envelope-from amit@phpandmore.net) Received: by mail-wr0-x244.google.com with SMTP id z1so2471932wre.1 for ; Sun, 01 Oct 2017 11:36:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=phpandmore-net.20150623.gappssmtp.com; s=20150623; h=subject:to:newsgroups:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=PCn/P7PUUlC5cQVPsFv6Zd4Fq3GxXmP6vnEtRA9eaUw=; b=UiKhcpLuvwOK/JES/+cQeiLmsIN+FNwgfZSfMXVgMagTTmBQHJsWa+MDEScQWbMhJJ bTF2a087bhnZjfBia3Cda7QHtvcBiiJX1YYtNYy2nZmtXV5omLWRZdJXzcK6yO9vEl9W wZ1EYffOmAbB/8N7HiCebcxNU0qi7FgCAMwSfPKBU+7dJMWjcdSqYyobHlsi5E8fb3ok PJyiwFtNcPZ5nFJUrvX/ErayRh2V44krYYBwFoN5vx0SDZ+6iEafol4vfthoyzHt5opc n33z4CVtnWy5vSqrudo+PdmXr6kwgiQn6zSvXSKHCZY/pxVyAt1drDkBR9IRU4q0NgcX vAHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:newsgroups:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=PCn/P7PUUlC5cQVPsFv6Zd4Fq3GxXmP6vnEtRA9eaUw=; b=DGsXovAorMKhAjgmXIgb9hCDa3ei7If/u7CtMciWFVR9ARYaD8cdCCsyBofDTrboPG NdlnAeyPGyBcENjp7rqVKAuBz++y7AxE+o/zYDRCAgPs8n83woeDnCaRYM4kFHNlBBo3 Paak9lTmTF8Ne5h6CpKbHobkz0B7eqWcMpPZn1CG4LSfCVcmAfGncQlVylO3IdNJPAEA TjLozqp3fYQcJCbmP9hn8OqNAuMBi2T94x3Qf0lwJkAP0DVa4k7c1dkBj4zXQ3I/ZFN1 M9dMPBNH/HRBIGlnujXtrOZ6/CE/dlYWc518mffDBonQK9Vy1g+OxTPB321gkP/mrmaA t3iA== X-Gm-Message-State: AHPjjUhQq4dzldlHWrcb7c/kxjDTyP+oqq0qrjoVgnDlVUwkp7PUOt5a UdvZStIr5fFYHLYxhW7xtltCtgt17AQ= X-Google-Smtp-Source: AOwi7QALUA6/4P2jk52yRd4k635IWJTLg+DJL1HqVt8Xyq7oTjVEI976MkyITUDfkttM775datBliw== X-Received: by 10.223.199.18 with SMTP id k18mr10078105wrg.145.1506882962989; Sun, 01 Oct 2017 11:36:02 -0700 (PDT) Received: from [10.0.0.1] ([94.230.86.101]) by smtp.gmail.com with ESMTPSA id t36sm16899953wrc.28.2017.10.01.11.36.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Oct 2017 11:36:01 -0700 (PDT) Subject: Re: Debugging A Port To: freebsd-ports@freebsd.org Newsgroups: gmane.os.freebsd.devel.ports References: <20171001174256.GI86601@home.opsec.eu> From: Amit Yaron Message-ID: <4375b67f-92a8-6b9f-989a-05cb6e0e5352@phpandmore.net> Date: Sun, 1 Oct 2017 21:35:53 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <20171001174256.GI86601@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 18:36:05 -0000 Thanks, It seems to work. On 01.10.2017 20:42, Kurt Jaeger wrote: > Hi! > >> What action will make the Make command to recompile a source file? > > That depends on the port, there's no generic way to say. > > Basically, the port framework adds a wrapper of targets > around the upstream source Makefile and those targets can shield > a recompile from happening. > > What sometimes work is this: > > cd work// > make > From owner-freebsd-ports@freebsd.org Sun Oct 1 18:53:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF3C0E2C04C for ; Sun, 1 Oct 2017 18:53:34 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F5CD6AD73 for ; Sun, 1 Oct 2017 18:53:33 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id C95D5A0FC; Sun, 1 Oct 2017 20:53:29 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 66DD1A0F8 for ; Sun, 1 Oct 2017 20:53:29 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 01 Oct 2017 20:53:29 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: <20171001172437.32f4a2c1@gumby.homeunix.com> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <5813dd8ee208549f2a96672723d47532@acheronmedia.com> <20171001172437.32f4a2c1@gumby.homeunix.com> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 18:53:34 -0000 On 2017-10-01 18:24, RW via freebsd-ports wrote: > > Do you mean as opposed to installing the dependencies from the > repository, or are you saying that it rebuilds them? Poudriere builds isolated, in jails. That means it's not reusing packages installed on the host, nor from another repo, if those are needed as (build) dependencies. Unless of course it grew this ability recently and I'm gravely mistaken, but I don't know of such addition. -- Vlad K. From owner-freebsd-ports@freebsd.org Sun Oct 1 21:34:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B7BBE2F1ED for ; Sun, 1 Oct 2017 21:34:55 +0000 (UTC) (envelope-from dpd@ixsystems.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E636A70016 for ; Sun, 1 Oct 2017 21:34:54 +0000 (UTC) (envelope-from dpd@ixsystems.com) Received: by mailman.ysv.freebsd.org (Postfix) id E2460E2F1EC; Sun, 1 Oct 2017 21:34:54 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1CE3E2F1EB for ; Sun, 1 Oct 2017 21:34:54 +0000 (UTC) (envelope-from dpd@ixsystems.com) Received: from mx.ixsystems.com (mx.ixsystems.com [12.229.62.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN ".", Issuer "." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BCD4970015; Sun, 1 Oct 2017 21:34:54 +0000 (UTC) (envelope-from dpd@ixsystems.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by mx.ixsystems.com (Postfix) with ESMTP id 3y4z8t1PYCzCqJ1; Sun, 1 Oct 2017 14:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems.com; h=x-mailer:date:date:message-id:subject:subject:mime-version :content-type:content-type:from:from:received:received:received :received:received:received:received; s=dkim; t=1506893682; x= 1508708083; bh=88r9BBCPnFLJYOumkVqOrVx9WuOa2GjvBHyoTuyAQio=; b=I 2UFBVJbAHmvN/tean/K9yC4wlGFxdIk8hSfSaFJgd64Yu40iT+td7T28SPvZ3EJH y5rcGPSm+PRb/7OwDKdBt0sU+sLM4wRtL+pt9JnlQuISlg0x1sSLKNQ2dBAxrHSN pjxZMCyhXmCVDHR0nVtSYY3zy2hqeZFpXMkbXiJv6kBvbqH5iQ25SbQfIONUgBmK kmZZOK9dvDFTI3QNS/VhnC3nNkaQrJAcp3ga7JZTQMVe6+s4WPMwUlVwt3WtkQCb QDZkd4200HQH2OID54bDT9dtNiaa2haGKm14+K67udTvz0en4AmOGrayYUHbmlvm ck+O8WR3yZFeeT3dAeSzQ== X-Amavis-Modified: Mail body modified (using disclaimer) - mx.ixsystems.com X-Virus-Scanned: Scrollout F1 at ixsystems.com Received: from mx.ixsystems.com ([127.0.0.1]) by localhost (mx.ixsystems.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id B_1oZGVkXbS3; Sun, 1 Oct 2017 14:34:42 -0700 (PDT) Received: from zimbra.ixsystems.com (mail.ixsystems.com [10.246.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ixsystems.com (Postfix) with ESMTPS id 3y4z8f5gK7zCprG; Sun, 1 Oct 2017 14:34:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zimbra.ixsystems.com (Postfix) with ESMTP id 964684600C0; Sun, 1 Oct 2017 14:34:42 -0700 (PDT) Received: from zimbra.ixsystems.com ([127.0.0.1]) by localhost (zimbra.ixsystems.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 5mRxzTBfCDQI; Sun, 1 Oct 2017 14:34:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zimbra.ixsystems.com (Postfix) with ESMTP id 770A94600C7; Sun, 1 Oct 2017 14:34:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at ixsystems.com Received: from zimbra.ixsystems.com ([127.0.0.1]) by localhost (zimbra.ixsystems.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ygsUttj7s-Fr; Sun, 1 Oct 2017 14:34:41 -0700 (PDT) Received: from relativity.dpdtech.com (vpn-2490.ixsystems.com [10.249.0.10]) by zimbra.ixsystems.com (Postfix) with ESMTPSA id 19AC64600C0; Sun, 1 Oct 2017 14:34:40 -0700 (PDT) From: "David P. Discher" Content-Type: multipart/signed; boundary="Apple-Mail=_0B496595-4962-4341-AC2A-883BB43C7D13"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FreeBSD Port: sudo-1.8.21p2 - 1.8.21p2 SegFaults Message-Id: <4B124D5E-E350-4B71-B3F2-782F5AC166A1@ixsystems.com> Date: Sun, 1 Oct 2017 14:34:40 -0700 Cc: ports@FreeBSD.org To: garga@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 21:34:55 -0000 --Apple-Mail=_0B496595-4962-4341-AC2A-883BB43C7D13 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Renato & ports : I was just stumble over this, with 12.0-CURRENT r323934, sudo 1.8.21p2 = SegFaults when run in a bhyve VM - however, seemly on bare metal, its = fine. sudo-1.8.20p2_3 runs just fine in bhyve VM. There are all my own builds = of 12- and ports (via poudriere). I recompiled sudo on the Bhyve, and = still had the same issue. -- David P. Discher =E2=80=A2 dpd@ixsystems.com Director, Information Technology iXsystems, Inc. Office: 408.943.4100 x150 Mobile: 408.368.3725 --Apple-Mail=_0B496595-4962-4341-AC2A-883BB43C7D13 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZ0V9wAAoJEMBp/cpE3y/SzccQAKwU/PRcUout+vb7kSywRPsb iqgEQ1dh31jNt3tMQwgZC3mh8DfvNXbkkMKA2o44gxr4OS7IqfqXA1zyKzxORSd1 4vJuAtoG6354S5s+9tIWLqPjyAZ54L9MRmO/QWIz0gomM2JDmBLAh61pkrlJspqU 2xF483IGzq9NPMmbCR8oh+hjfPOXDm4KfHW3vDZ+Ma65jrXFW8YzRwoRHGAmgVEs HWOXfDGk+H0Eg/ZvYSmbkFgK+NJ60O1XNbFnPLee7X5D+NA+KupCDyhgHdHNwnmM uF3C2lMX7+LrIqrATC+06f6jo4dpPQ0idYin1BlJ0UFx2gesZ/cRavb2doXYivOk 2+DdGEOeyjoRXyix/GbCMoDn/8oV0b0jiPlmw5kNQqKFAQac8DwAHDXGrYCJ0fHu t76VLDRxLm4WBZh3h5v3eLi9cnskgOhOO8EbXThtbbgpZZMcFPn8VOhZ1bMk11am RcltZUWChMPZgOWZ/odirq+DSvydf+4M8fo1/WI/viUqksyEWAINsA5edGf38vEt DMGA4NdsNxCtMgYPZuYBWRYFllk2EeU0c0cYSAJ4ucXVfqEywPLtLD0T/3zq2NcG 72FLgSQ7aUAJR4a6G0bYlXIB6dCBqzReNsIeHZYdeEVoCh8x3zi+shrjfUQjQIRZ 8XkVXUXhCJ+B0AmZEOxn =B5qM -----END PGP SIGNATURE----- --Apple-Mail=_0B496595-4962-4341-AC2A-883BB43C7D13-- From owner-freebsd-ports@freebsd.org Sun Oct 1 22:19:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D23F7E2FED2 for ; Sun, 1 Oct 2017 22:19:55 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A7E9D7120B for ; Sun, 1 Oct 2017 22:19:55 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A6FFAE2FED1; Sun, 1 Oct 2017 22:19:55 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6914E2FED0 for ; Sun, 1 Oct 2017 22:19:55 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D2CF7120A for ; Sun, 1 Oct 2017 22:19:55 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr0-x229.google.com with SMTP id o44so910896wrf.11 for ; Sun, 01 Oct 2017 15:19:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=fHTW6BNEG4ouOVFpV7HR3qBVAUotrsKeuE3awBLkN9s=; b=Ct5RzmKJqQb2vWV4ARbOkr0DwpPOS5IyxH/QDnixlwHa80p0++9DrMQfPE2cdN3/vW qkcgyOWarlJQA6qVnjz9xd3PzIQnAojNP4H+vqZ56871tdoN3J5pqb3PNvlQbWitP+oN Y/S24AgwJpQM6C4sQwNyEQD15UKrEljT4ZJtSwPSDDsvuCZBfb84Cv2LzAV0/51ry0Vp MwjhaW7LY5afXNGDUVpqEPHi8mxUdshUzNdypFoG4JBr9pJlVc9cOMGZR6iQxa9gegJg qtZ3EAs4wh5PecjSSPcxzEWJil0NEDbKuAt6NwA5gi1SqkBOPha2i8396M63j6PKLFpw 6o6Q== X-Gm-Message-State: AMCzsaWlZMoEuq4KN06j5Ylrk6Qyoqnr6PYWCTW5PRpfAwG1SGl3+H/5 jasi1yR2RUP+VL878rPrmo1k3g== X-Google-Smtp-Source: AOwi7QALgwK+B/LUHnL5A7pbeeK5UknDeXrm0BWR1cGUaQwkkuEf7QYfZHBcos7wm0heObeoButbNA== X-Received: by 10.223.176.199 with SMTP id j7mr882538wra.58.1506896392670; Sun, 01 Oct 2017 15:19:52 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id a19sm10362030wra.64.2017.10.01.15.19.50 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 01 Oct 2017 15:19:51 -0700 (PDT) Date: Sun, 1 Oct 2017 23:19:49 +0100 From: RW To: ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171001231620.724cb858@gumby.homeunix.com> In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <5813dd8ee208549f2a96672723d47532@acheronmedia.com> <20171001172437.32f4a2c1@gumby.homeunix.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 22:19:55 -0000 On Sun, 01 Oct 2017 20:53:29 +0200 Vlad K. wrote: > On 2017-10-01 18:24, RW via freebsd-ports wrote: > > > > Do you mean as opposed to installing the dependencies from the > > repository, or are you saying that it rebuilds them? > > Poudriere builds isolated, in jails. That means it's not reusing > packages installed on the host, nor from another repo, if those are > needed as (build) dependencies. I meant installing up-to-date packages from the *local* repository. So if only Firefox needs to be updated would Poudriere first install Firefox's dependencies into the jail from locally generated package files before building Firefox. If that happens then there wouldn't be much incentive to use anything from the host as any package installed on the host would be in the local repository - you'd just save a few installs. From owner-freebsd-ports@freebsd.org Sun Oct 1 22:34:06 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 600B7E30288 for ; Sun, 1 Oct 2017 22:34:06 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F582718DB for ; Sun, 1 Oct 2017 22:34:05 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id 55B88A1A4; Mon, 2 Oct 2017 00:34:02 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id D3C04A1A0 for ; Mon, 2 Oct 2017 00:34:01 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 02 Oct 2017 00:34:01 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: <20171001231620.724cb858@gumby.homeunix.com> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <5813dd8ee208549f2a96672723d47532@acheronmedia.com> <20171001172437.32f4a2c1@gumby.homeunix.com> <20171001231620.724cb858@gumby.homeunix.com> Message-ID: <24b25edafb33c4ca8a86bd1022258a68@acheronmedia.com> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 22:34:06 -0000 On 2017-10-02 00:19, RW via freebsd-ports wrote: > I meant installing up-to-date packages from the *local* repository. So > if only Firefox needs to be updated would Poudriere first install > Firefox's dependencies into the jail from locally generated package > files before building Firefox. Poudriere builds repositories and yes, uses any package already built in that repository if it's a build dependency for another. Note that you have multiple repos, built with different base jails, different ports trees, different sets of packages, options, make.conf options. But even for single machine use, it allows simple building of any list of wanted packages, it makes sure those and their dependencies are built, up to date (relative to the ports tree it's configured to use), and kept as a persistent repository. You can even delete a package txz from the repo manually, on next bulk run it will simply rebuild what's missing. -- Vlad K. From owner-freebsd-ports@freebsd.org Sun Oct 1 22:49:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22E3EE304DC for ; Sun, 1 Oct 2017 22:49:35 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BBC4E71CAB for ; Sun, 1 Oct 2017 22:49:33 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:8d79:2312:1fde:a9c1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 18F943134 for ; Sun, 1 Oct 2017 22:49:22 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> From: Matthew Seaman Message-ID: <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> Date: Sun, 1 Oct 2017 23:49:14 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HW4ioRi39kdLORWTbE2Ls8JVc0Uqxueo4" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2017 22:49:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HW4ioRi39kdLORWTbE2Ls8JVc0Uqxueo4 Content-Type: multipart/mixed; boundary="pGV6RIIqcbg2ucMgrPVlMulHC8FMcVELx"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> Subject: Re: Status of portupgrade and portmaster? References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> In-Reply-To: --pGV6RIIqcbg2ucMgrPVlMulHC8FMcVELx Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 01/10/2017 11:34, Carmel NY wrote: > 1. Does it determine out-of-date update packages automatically or does > the user have to determine that what is out-of-date and feed them to po= udriere > manually and in the proper order? Automatic. > 2. From what I have read, the user is required to install each package > manually. Is that correct? Poudriere builds a repository. You then have to type 'pkg upgrade' or 'pkg install foo' to update your live system. Most people do not find this particularly taxing. Cheers, Matthew --pGV6RIIqcbg2ucMgrPVlMulHC8FMcVELx-- --HW4ioRi39kdLORWTbE2Ls8JVc0Uqxueo4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ0XDyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATrFcP/1QO4AL9MUpDYraOXJi098LP y1W3HrptfWITVUx7PGW5Vdle0pRuItjsNncPLZFfhnHv+5W8HlBZk64J4ofPXiUS 1vVfgVMUIsI5XUIaoSoBsE+q+a353MIxn4zTOD4QWJ6cjJtGNdjIZlwP3QkYQk5V Qgf1O0hRmMoMgwuSxiLeKr3+SimG3p5zK4csSY/jseHuBTFIabdCzv7zjS5vj2ap jMV979vQSBb/xMZJjP2M8UN704Q66uImJdNmZNBKcvNJscPShfM/F47h10aJc7bV ZYGh+RlnyDryIwa28/oLnaF+bx8SAbzPFIvEsD5OFeDzc0VCrBU3MzRSE8pYWDxc 6BEZyo/UL8/FoIAVvSCKDEj1Fwq1oWWQl9QcXvWzT6/FVmEPvBb2fXx0lv6+ze6T aHe7uKJPQXhS2KwjIUBjdmYAN9O4cHGC8L06jXwPlMlODQe4+sn2KWZUWnxZ2yAw nVvrE9A9QIHsn/+yQgtYX2hxq+Wzu2ih7y5iwf3Tm8tH+bzLl03KSp2KzRU4lOS6 b0IRilwnkF/N2l2n1wBmVj7TC+0lgfRpt3ucF8LvA6s6gdRbel/1sJUpo3sABzQX wpQMew+VhttFmIhWO7T8HCKnYujqOd2z88d4ugrv4QadC11PuVIypAQ1udNNGSDE vawt5hfKoNwGGN59PZvV =RgdZ -----END PGP SIGNATURE----- --HW4ioRi39kdLORWTbE2Ls8JVc0Uqxueo4-- From owner-freebsd-ports@freebsd.org Mon Oct 2 00:54:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9199DE32826 for ; Mon, 2 Oct 2017 00:54:28 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71C1174CA1 for ; Mon, 2 Oct 2017 00:54:28 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3y53TD1s6DzPg; Sun, 1 Oct 2017 19:49:20 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3y53TC3vMlzGsS; Sun, 1 Oct 2017 19:49:19 -0500 (CDT) Date: Sun, 1 Oct 2017 19:49:19 -0500 From: "Matthew D. Fuller" To: Marco Beishuizen Cc: Thomas Mueller , freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002004919.GL53186@over-yonder.net> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <201709290909.v8T99QtU006095@mxdrop301.xs4all.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 00:54:28 -0000 On Fri, Sep 29, 2017 at 09:21:31PM +0200 I heard the voice of Marco Beishuizen, and lo! it spake thus: > > Using portupgrade every day and still works great. Tried portmaster > once but liked portupgrade more. I use poudriere just for testing > ports. I also use portupgrade constantly on several systems, and portmaster occasionally for some special cases where it has advantages. I also use poudriere on a lot of systems. Actually, most, nowadays. And I'm extremely happy with it. But I expect the systems I'm running straight out of ports now will continue to do so for a very long time, since poudriere just won't fit at all. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-ports@freebsd.org Mon Oct 2 07:03:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1733BE38392 for ; Mon, 2 Oct 2017 07:03:31 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id BA61C8203D for ; Mon, 2 Oct 2017 07:03:30 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id C089753C2; Mon, 2 Oct 2017 07:03:21 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: Jonathan Chen Cc: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> From: abi Message-ID: Date: Mon, 2 Oct 2017 10:02:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506927802; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=7M+cHRPC8OsFH6eHMEmX9cpDbr89IMmgUPASxdNUA2w=; b=kLpxROxo5dCNjp5Bdq/LhNoPWfCGeo9IZXXSxKKdscyLz2JWf9SF7olziCiQ+yKhe1LaHv uMrQ2vY8QvS1M4ZysvZJ0Gt5rryS6+EbiXYYe6TSZiMPY0VDlGU4NKx+ZL8xueZcqGcuGC R9Iy/iQH9HonitTCbKLPv0Lj00KQxXY= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 07:03:31 -0000 01.10.2017 01:44, Jonathan Chen пишет: > On 1 October 2017 at 11:29, abi wrote: >> 30.09.2017 20:06, Kevin Oberman пишет: >>> >>> As a result, I am no longer able to track HEAD and, if the issue is not >>> resolved in some manner before 11 support ends, will be forced to move >>> from >>> FreeBSD after an using it for over 2 decades. I certainly hope that this >>> is >>> not what happens. >> >> Is it absolutely necessary to be so overdramatic ? synth is rather young >> project and it's failure was very probable - written on long dead language >> and supported by 1 person. It can't even be replacement for portmaster as >> contains only preliminary support if port options. > What sort of port options can portmaster support better than synth? 1. When port doesn't have options cached portmaster invokes dialog4ports (poudriere can't do it in proper way, synth doesn't do it at all) 2. When options become outdated portmaster invokes dialog4ports 3. portmaster gives me summary what it would like to do 4. portmaster shows why it wants to build port A - it gives me dependency chain. For example I spent 2 hours trying to figure what's going on with poudriere (it pulls TEST dependencies - why?) So, I'd say we have only 1 tool designed for end user. From owner-freebsd-ports@freebsd.org Mon Oct 2 08:31:05 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B3E6E397A9 for ; Mon, 2 Oct 2017 08:31:05 +0000 (UTC) (envelope-from philip@trouble.is) Received: from weatherwax.trouble.is (weatherwax.trouble.is [IPv6:2a00:dd80:3c::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E882784288; Mon, 2 Oct 2017 08:31:04 +0000 (UTC) (envelope-from philip@trouble.is) Received: from rincewind.trouble.is (rincewind.trouble.is [88.198.44.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 3y5Fjy5697z11Nl; Mon, 2 Oct 2017 08:31:02 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, from userid 1001) id 3y5Fjy08tczGbC; Mon, 2 Oct 2017 08:31:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trouble.is; s=rincewind; t=1506933062; bh=g38DyqPSOPp2jhz9eIm0eSmnGTocS+9Q0cLdYWSw+jg=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=jQyShyZB4VILvyW3pxAzQFkl0Oiw7WIGSt0b0f9NqTl0RqyXSJhFlItKpRvXpD5ns nW6Xi0ChWFyFeFNEkjD1m6JXsT978wmghLY+Qny7Cm6Ru+krfGeP4iB5IzMzsAVkW3 4PoMi+W8jFSEGs/xZRX5HTeSyxLm6fYX1EyvwSXo= Date: Mon, 2 Oct 2017 10:31:01 +0200 From: Philip Paeps To: Mathieu Arnold Cc: freebsd-ports@freebsd.org Subject: Re: [HEADUP] FLAVORS landing. Message-ID: <20171002083101.GA39534@rincewind.trouble.is> Mail-Followup-To: Mathieu Arnold , freebsd-ports@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: 2CD1 92C2 6EE7 B7D1 F552 6619 31AE B9B5 FDBB CB0E X-Date: Today is Setting Orange, the 56th day of Bureaucracy in the YOLD 3183 X-Phase-of-Moon: The Moon is Waxing Gibbous (87% of Full) X-Clacks-Overhead: GNU Terry Pratchett Organization: Happily Disorganized User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 08:31:05 -0000 On 2017-09-26 16:05:08 (+0200), Mathieu Arnold wrote: >**Do not commit FLAVORS to any ports, a hook will prevent it, that >being said, do try it and test what can be done.** There also seems to be a hook preventing new py3-* ports being added. How should maintainers of Python3 ports proceed when their ports have new py3-* dependencies? It's not immediately obvious to me from the wiki. Thanks. Philip -- Philip Paeps Senior Reality Engineer Ministry of Information From owner-freebsd-ports@freebsd.org Mon Oct 2 09:07:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2E1CE3A42D for ; Mon, 2 Oct 2017 09:07:46 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04olkn0806.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4c::806]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5972F33C for ; Mon, 2 Oct 2017 09:07:46 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XdnTTd4n0iHJAaGD0JpBiSoGHCEdL473Lj2nFV4GKXE=; b=XmL33Zj8+TAQp+TLSGTQynAAP4x5UBFBj7z1Ll1zwrugJdJHOS047lRmFPNs5sgldNhGDjW1W5PtkwE6WLZpVdEe+zGOpRKnCVMoa9L/DJ3SJqIgqPv+UQUyG+P0qnUK22lmeEsp7B26xY25+escND4A5WCeQQbWDNNvgjrERdrkpz+tCUX/l6VCWd5kBUojafmVrnJl35fOVS6XE8AeLQOmkeWsh08l3kAxBaDNQbXcs4wo/2nNoDzYtL6mWp47sWTPMqe/FMVXF+zUVzYfMIu43OpfA5nRWlezKP1qrpPiONDFKITzq5Kpy8Vsy3b0Tv6GhnUAUKrjivQq2ww79g== Received: from SN1NAM04FT007.eop-NAM04.prod.protection.outlook.com (10.152.88.57) by SN1NAM04HT058.eop-NAM04.prod.protection.outlook.com (10.152.88.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.56.11; Mon, 2 Oct 2017 09:07:28 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.88.55) by SN1NAM04FT007.mail.protection.outlook.com (10.152.88.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.56.11 via Frontend Transport; Mon, 2 Oct 2017 09:07:28 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.20.0077.018; Mon, 2 Oct 2017 09:07:27 +0000 From: Carmel NY To: FreeBSD Subject: Re: Status of portupgrade and portmaster? Thread-Topic: Status of portupgrade and portmaster? Thread-Index: AQHTOQa5V6RAlsDMdkWBuhE2Y+Zwrw== Date: Mon, 2 Oct 2017 09:07:27 +0000 Message-ID: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> In-Reply-To: <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:B95594B67FE7E795ADBDFE47605964CF2FA0D38DAD445530F7A944129B56640D; UpperCasedChecksum:56C1292152BDA64707EF4D7EA79818BE49282B47087E4A01EA97CD37FD5A64D4; SizeAsReceived:7729; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [P8BLPfpSGNsYG+PNhwfdE7VnUCWm+QXR] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT058; 6:qyWYmWJdt6h1SIqUrfGQzAQrPgTcVr7IijQLjkV6PxaO6nBNAP47KvdVEGVfMefsjfm/K7sfXBjYtOPHKDnkU6rWYkYZc0oJy2rStJoA7QnhpIbqgRSpTzmSkZqNssGDaIqPNIV9UAB7oRCuytSnjuCsPD9/yJIpxFtbTzoDdJgg1+sRNz+Zd0QXBsi5iulKhA1ZGhC/LWL0mzFNCH72nJGqaM8FT0J2maWuWGdu0NE+TiL4UG/JURMotfaS+ScM3L003xMsuVKMMCoPkKsrcbutyTwZVMTjno6m+VjahpJBaLlRih8ouGVrq+uKoR0FjyOFDYBN4hg5vOnaBNYSpQ==; 5:TvhgFZC6zvorCPwSpZSVAg7egWFrRWKjEuSnIqdNFK9mClYnk1fnpWSGh9HnuEi6tyXfQ+30x4NM5waIlSQSXnuYxM1OSHYrJy6AZP1UMZtdlxfjzq/WuXFjKyjTjxHGehLWhmBKXzPtveJii5Pqeg==; 24:Z3Uh6Ry2EIAoNUeoXb3gZm2fkm8nYz+8bXfFQwIHTAFKbaUUvT6OWfOzlzrOg+B+P1uRKLeQIbM6hYTwN9zcXS4WpYKbjIqH10e+onLgIu8=; 7:sN+uK1be6a+zhQ/ELhB6DBoBIrc9tHu2nkvAoRcnhIopxtVyuEnMCxvpAFSMqF8jfcdMbPgUePjBZ3CYYo3ygXLd8MJ5DyPxF5M/MAjiAvw1Pw/FZ5y4PSROghgkKxYbmT3GzlYliZHkhyhefsMeIJL3BHCkloxx7WSe3+TDuVAaML1baZIMIlfGx4wjVY9B2QgWNaNK4FPUjp5cqI/7pDfeOSlqLnHbeSZ1AixYcGQ= x-incomingheadercount: 47 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: 7296dc9a-ea69-4a78-1525-08d509750076 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:SN1NAM04HT058; x-ms-traffictypediagnostic: SN1NAM04HT058: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SN1NAM04HT058; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1NAM04HT058; x-forefront-prvs: 0448A97BF2 x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT058; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <936FA94ED71B42499D4BF509C7736953@namprd20.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2017 09:07:27.7136 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT058 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:07:46 -0000 T24gU3VuLCAxIE9jdCAyMDE3IDIzOjQ5OjE0ICswMTAwLCBNYXR0aGV3IFNlYW1hbiBzdGF0ZWQ6 DQoNCj5PbiAwMS8xMC8yMDE3IDExOjM0LCBDYXJtZWwgTlkgd3JvdGU6DQo+PiAxLiBEb2VzIGl0 IGRldGVybWluZSBvdXQtb2YtZGF0ZSB1cGRhdGUgcGFja2FnZXMgYXV0b21hdGljYWxseSBvciBk b2VzDQo+PiB0aGUgdXNlciBoYXZlIHRvIGRldGVybWluZSB0aGF0IHdoYXQgaXMgb3V0LW9mLWRh dGUgYW5kIGZlZWQgdGhlbSB0bw0KPj4gcG91ZHJpZXJlIG1hbnVhbGx5IGFuZCBpbiB0aGUgcHJv cGVyIG9yZGVyPyAgDQo+DQo+QXV0b21hdGljLg0KPg0KPj4gMi4gRnJvbSB3aGF0IEkgaGF2ZSBy ZWFkLCB0aGUgdXNlciBpcyByZXF1aXJlZCB0byBpbnN0YWxsIGVhY2ggcGFja2FnZQ0KPj4gbWFu dWFsbHkuIElzIHRoYXQgY29ycmVjdD8gIA0KPg0KPlBvdWRyaWVyZSBidWlsZHMgYSByZXBvc2l0 b3J5LiAgWW91IHRoZW4gaGF2ZSB0byB0eXBlICdwa2cgdXBncmFkZScgb3INCj4ncGtnIGluc3Rh bGwgZm9vJyB0byB1cGRhdGUgeW91ciBsaXZlIHN5c3RlbS4gIE1vc3QgcGVvcGxlIGRvIG5vdCBm aW5kDQo+dGhpcyBwYXJ0aWN1bGFybHkgdGF4aW5nLg0KDQpGcm9tIHRoZSAicGtnLWRlc2NyIiBm aWxlOg0KDQpwb3VkcmllcmUgaXMgYSB0b29sIHByaW1hcmlseSBkZXNpZ25lZCB0byB0ZXN0IHBh Y2thZ2UgcHJvZHVjdGlvbiBvbg0KRnJlZUJTRC4gSG93ZXZlciwgbW9zdCBwZW9wbGUgd2lsbCBm aW5kIGl0IHVzZWZ1bCB0byBidWxrIGJ1aWxkIHBvcnRzDQpmb3IgRnJlZUJTRC4NCg0KV2hpbGUg aXQgd2lsbCB1bmRvdWJ0ZWRseSB3b3JrLCBpdCBpcyBzdGlsbCBtb3JlIGNvbXBsZXggdGhhbiB0 aGUgYXZlcmFnZQ0KZGVza3RvcCB1c2VyIHJlcXVpcmVycy4gU3ludGggZml0cyB0aGUgYmlsbCBu aWNlbHkgYnkgYmVpbmcsIGZvciB0aGUgbW9zdA0KcGFydCwgZWFzeSB0byB1bmRlcnN0YW5kIGFu ZCBydW4uIEkgYW0gYWxyZWFkeSBvbiBteSBmb3J0aCAicG9ydHMgbWFpbnRlbmFuY2UiDQpwcm9n cmFtIGhhdmluZyB1c2VkIHBvcnRtYW5hZ2VyLCBwb3J0bWFzdGVyLCBwb3J0dXBncmFkZSBhbmQg bm93IHN5bnRoLiBBdA0KdGhpcyBwb2ludCwgSSB3b3VsZCBhbG1vc3QgcmF0aGVyIHN3aXRjaCB0 byBhIG5ldyBPUyBiZWZvcmUgYWJhbmRvbmluZyBzeW50aA0KZm9yIHNvbWV0aGluZyB0aGF0IElN SE8gaXMganVzdCBvdmVya2lsbCBmb3IgdGhlIGF2ZXJhZ2UgdXNlci4NCg0KSnVzdCBteSAywqIu DQoNCi0tIA0KQ2FybWVsDQo= From owner-freebsd-ports@freebsd.org Mon Oct 2 09:23:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A19CFE3A7D6 for ; Mon, 2 Oct 2017 09:23:23 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta01.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 77A32E42 for ; Mon, 2 Oct 2017 09:23:22 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([74.134.208.22]) by cmsmtp with ESMTP id ywwUdB2oDCCQCywwWdzaTC; Mon, 02 Oct 2017 09:23:16 +0000 Date: Mon, 02 Oct 2017 09:22:22 +0000 From: "Thomas Mueller" To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com>, <20171001041404.GD27224@lonesome.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> Subject: Re: Status of portupgrade and portmaster? X-CMAE-Envelope: MS4wfOs25LbggmiXWEZ1Hy9wcH3a4hSykp8JKTtVk1TkqZN6PFdHc3GcIy1lLyNAcLw+wICNgSl6zTCF8h/0SfCQ9BkuF4ItJhkiTUugzegAK3kOPPf1bNfW dBh3L0sR9LApaBViy4UmuUYbMjYB0IlEdahlRyfmheDtOMa9N1CHYlSj X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:23:23 -0000 from abi: > > What sort of port options can portmaster support better than synth? > 1. When port doesn't have options cached portmaster invokes dialog4ports > (poudriere can't do it in proper way, synth doesn't do it at all) > 2. When options become outdated portmaster invokes dialog4ports > 3. portmaster gives me summary what it would like to do > 4. portmaster shows why it wants to build port A - it gives me dependency > chain. For example I spent 2 hours trying to figure what's going on with > poudriere (it pulls TEST dependencies - why?) > So, I'd say we have only 1 tool designed for end user. Downside of dialog4ports is burying options in a tree under /var/db/ports not intended for direct modification by user. I much prefer direct non-dialog editing of options, such as is done in pkgsrc and Gentoo portage. I recently got into a circular-dependency mess using "make config-recursive" multiple times on each port. I had to delete /var/db/ports/* but keep empty /var/db/ports and put the options in /usr/local/etc/synth/LiveSystem-make.conf But I could still be screwed when options become outdated or new options arise. Tom From owner-freebsd-ports@freebsd.org Mon Oct 2 09:26:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 533B9E3A91F for ; Mon, 2 Oct 2017 09:26:49 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id 015AEFC6 for ; Mon, 2 Oct 2017 09:26:48 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 18B9D548E; Mon, 2 Oct 2017 09:26:45 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: FreeBSD , Carmel NY References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> From: abi Message-ID: <77f800a1-0806-acb1-2854-33cba3793c39@abinet.ru> Date: Mon, 2 Oct 2017 12:26:02 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506936406; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=yjmHhgzTPN5kRXooEnZvI6q59uEWnBq1pM3VdTwpWAE=; b=GMSyq1+naQ3vhwxQGEgGWyfdge9rIXJ/4kADZdYv1IRLgltz5NyBA6OAgikMU6WGwNgLqI 6Kmj9EN8XDYRDus49M1nyZ3L0Di4MWge+ieuZzQ8jpJIJ+9bNp3Y0UUOtj6BvULHTIGmXt 8qmOfeUC2LysGyVBq6VaAPmr4VDuZMs= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:26:49 -0000 02.10.2017 12:07, Carmel NY пишет: > While it will undoubtedly work, it is still more complex than the average > desktop user requirers. Building from ports is already more complex thing than one could expect from desktop user. I don't think ports are recommended way to keep system updated. It you use ports, you change port options (why would you use them if not), so you are on narrower path - non-default options are not QA tested, can conflict with each other and within dependency chain, etc > Synth fits the bill nicely by being, for the most > part, easy to understand and run. I am already on my forth "ports maintenance" > program having used portmanager, portmaster, portupgrade and now synth. At > this point, I would almost rather switch to a new OS before abandoning synth > for something that IMHO is just overkill for the average user. You know, this is open source, right? You may  pick up ADA stack, I'm sure J Marino will give you some ideas how to overcome ino64 issue. From owner-freebsd-ports@freebsd.org Mon Oct 2 09:28:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45470E3A9B1 for ; Mon, 2 Oct 2017 09:28:56 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8D0110AD for ; Mon, 2 Oct 2017 09:28:55 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id q124so9320869wmb.0 for ; Mon, 02 Oct 2017 02:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=T9XBWfu2TX7xZKu1jCbR91ooCn16aMnFzXVtsPcNWTE=; b=NhQysJgML1o2kX+NLPnbCKxciw/TB9dxGVdj/mELtJfWid4u7pIhcEmgbSvJcllFho KWgoM1EN+FH6bMoxbyMirDtOR9kI4AND5bu92QWtrSEj+xQfYlShGIB0UbKAEtwZ1JW5 DMSlR+69UsiERuBrvzSdpt5zCOPGx0N24Na8xMhFPpzv3LSkLlDx4ZTlXkEvEgUFdY8S xNDHkAIvo6inqTiFXgLxubTmr2h9YzaNrO6LJAYMGMBUobskgYKyC6dJFpdLuvwANSpF P5xiMDCHUufgPFZNH6MInbq6AR06DjZoIbGdy1OXm+CFm0rQQ5MvK0rk6oWTFACNjOfA okPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=T9XBWfu2TX7xZKu1jCbR91ooCn16aMnFzXVtsPcNWTE=; b=lKcuzoYjY5wt2katThNc6dZIENjriteKVAE7kpOEJ42hYhT4WWsk4a0UeiIBFAkEfa 2ao0meW8VeFSJ33BoHMfEJd2BMio9mw/hMDNdol14mxC39Nss3O89t8r89YfLLqp0pX1 0mpu+754D3O8FrfLWJ0W7UDmp4uH+3yH2xZxlmBh7bk11imLAXuVJMTSyXNlluCdSHqK dKry8kQPip62kT4kdeLixoaz9UcK8m6sNLRJVJ7vwRDQT1x/bwi/HX18M2zVglmvXcjG qQf2wqO9L7GxXfYEwXVK/PG10dujjavY25u6SN+XZmbddogz7iOghhK2RnM9tjBkNpqi qnIg== X-Gm-Message-State: AHPjjUj1A9WzE0bvZRJ/Uy3Wz9rVuX0EkWLwmC5QHZz1Fu/rzOCQcEgt PvpTTF332jRfC8rbSWUfbicc48eu X-Google-Smtp-Source: AOwi7QAimLPiRn58pAGWnkQTIN++dQMMMxzHA2OphU1XhfllMS1IDsCnt03dqViNsg2GWXOGXXeBfg== X-Received: by 10.80.136.165 with SMTP id d34mr19307324edd.296.1506936532253; Mon, 02 Oct 2017 02:28:52 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id c25sm9452756edb.57.2017.10.02.02.28.51 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Oct 2017 02:28:51 -0700 (PDT) Date: Mon, 2 Oct 2017 10:28:49 +0100 From: Matt Smith To: FreeBSD Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002092849.GA48518@gmail.com> Mail-Followup-To: Matt Smith , FreeBSD References: <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:28:56 -0000 On Oct 02 09:07, Carmel NY wrote: >On Sun, 1 Oct 2017 23:49:14 +0100, Matthew Seaman stated: > >>On 01/10/2017 11:34, Carmel NY wrote: >>> 1. Does it determine out-of-date update packages automatically or does >>> the user have to determine that what is out-of-date and feed them to >>> poudriere manually and in the proper order? >> >>Automatic. >> >>> 2. From what I have read, the user is required to install each package >>> manually. Is that correct? >> >>Poudriere builds a repository. You then have to type 'pkg upgrade' or >>'pkg install foo' to update your live system. Most people do not find >>this particularly taxing. > >From the "pkg-descr" file: > >poudriere is a tool primarily designed to test package production on >FreeBSD. However, most people will find it useful to bulk build ports >for FreeBSD. > >While it will undoubtedly work, it is still more complex than the average >desktop user requirers. Synth fits the bill nicely by being, for the most >part, easy to understand and run. I am already on my forth "ports maintenance" >program having used portmanager, portmaster, portupgrade and now synth. At >this point, I would almost rather switch to a new OS before abandoning synth >for something that IMHO is just overkill for the average user. > >Just my 2¢. > Of course if you did move to a different OS then the chances are you would be using a binary package repository and not compiling any software from source. So you wouldn't have any choice over the options that these packages were built with. If you are happy enough to do this then you may as well just abandon building ports on FreeBSD anyway and just use the pkg tool from the official FreeBSD repository. This is the easiest option surely. For what it's worth I've used both synth and poudriere and whilst poudriere is slightly heavier to use because of the requirement to create a build jail first, once that step has been done it's pretty much identical to using synth really. My workflow is simply this: poudriere ports -u (update the ports tree) poudriere bulk -j 11 -f pkglist (check for any updates and build any packages listed in the pkglist file) pkg upgrade (upgrade any upgraded packages) That's it. The same workflow on synth is: svn up /usr/ports synth build pkglist pkg upgrade Pretty similar if you ask me. OK you could use synth upgrade-system and do it in one command rather than two but then you're building everything on the host system and not a specific list. Also I like the extra pkg stage, it gives me a chance to see what pkg is about to do and abort it if it wants to do something insane. -- Matt From owner-freebsd-ports@freebsd.org Mon Oct 2 09:47:12 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1FBAE3ADAB for ; Mon, 2 Oct 2017 09:47:12 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id A2BF319F6 for ; Mon, 2 Oct 2017 09:47:12 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id C9D2554C6; Mon, 2 Oct 2017 09:47:09 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: Thomas Mueller , freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <20171001041404.GD27224@lonesome.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> From: abi Message-ID: <6ca7eaac-59e1-ad03-15ab-60234605b669@abinet.ru> Date: Mon, 2 Oct 2017 12:46:26 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506937630; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=BbL49t5DokbaOVSfqC9TYqx5FXjDHg2idkNX7km0UFI=; b=V2U5F4ePmXEms+64yRmK6N6YBPdqF6+Hn1GnsHVtSmbNNu3MqvReG3JUbaiK5wa+xmrvHt Ccz4jArXljAzAsJf/6qsWqzIqo/OD8xycYlTrmSjZdUdWKsdNQvuF7sqOE9t6ZsDptymLv vVrYLNAjZpTVjB378n6Jb+jyMiytoi0= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:47:13 -0000 02.10.2017 12:22, Thomas Mueller пишет: > > Downside of dialog4ports is burying options in a tree under /var/db/ports not intended for direct modification by user. Direct modification assumes you edit it directly, I leave this job for dialog4ports. > I had to delete /var/db/ports/* but keep empty /var/db/ports and put the options in > /usr/local/etc/synth/LiveSystem-make.conf And how you are going to support make.conf options ? Let's say, if you need custom ffmpeg or nginx, how many lines you need to put in that file? Probably 2, but they will be long. How are you going to be notified for new options ? nginx options changes fast and if they enabled by default, you *silently* receive them. Maybe changes will be incompatible with your custom build, like HTTPv2 without SSL. make.conf way is a long term failure. It's not Gentoo portage with meta flags. From owner-freebsd-ports@freebsd.org Mon Oct 2 09:51:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F09EE3AF98 for ; Mon, 2 Oct 2017 09:51:54 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F3C71CEA for ; Mon, 2 Oct 2017 09:51:53 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id AEFBEA78F; Mon, 2 Oct 2017 11:51:49 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 596BDA78B for ; Mon, 2 Oct 2017 11:51:49 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 02 Oct 2017 11:51:49 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> Message-ID: <436be05816210d94197b4171118ab029@acheronmedia.com> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:51:54 -0000 On 2017-10-02 09:02, abi wrote: > 1. When port doesn't have options cached portmaster invokes > dialog4ports (poudriere can't do it in proper way, synth doesn't do it > at all) What do you mean it can't? poudriere options -j jailname -p portstree -f /list/of/packages No? And if you re-run this step after each 'ports -u' and before 'bulk', it will raise dialogs for ports that have options changed. -- Vlad K. From owner-freebsd-ports@freebsd.org Mon Oct 2 09:58:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6756EE3B05F for ; Mon, 2 Oct 2017 09:58:29 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0ABCF207D for ; Mon, 2 Oct 2017 09:58:27 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 8F75E54E9 for ; Mon, 2 Oct 2017 09:58:23 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> <436be05816210d94197b4171118ab029@acheronmedia.com> From: abi Message-ID: <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> Date: Mon, 2 Oct 2017 12:57:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <436be05816210d94197b4171118ab029@acheronmedia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506938303; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=LdOWgweO7ykSYjZ14brjO3gXUVlKdwUXtjJ09DAW5j0=; b=emo7KDMzal7xemWeM3EWc+e+XOQ89/G4+L8v75IyigucgLOJAiWMVPvwv3jRnIRe2Gm4nF Cw5g8BUZoaJ8QKFiqeMMfMzjkKTGVA7w8QgpwIGEdOxPzwCoa6dMffunV11ceVxRImnwO1 Ti0ohqS0JatkncfNzhi1HUM624ArZIc= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 09:58:29 -0000 02.10.2017 12:51, Vlad K. пишет: > On 2017-10-02 09:02, abi wrote: >> 1. When port doesn't have options cached portmaster invokes >> dialog4ports (poudriere can't do it in proper way, synth doesn't do it >> at all) > > What do you mean it can't? > ' in proper way. Issues I encountered when switched to poudriere 1. Test deps pulled. I received very strange requests for some ports. 2. Dependency chain is not updated - if I disable B feature on port A, poudriere asks me for options of ports implementing B. I have to Ctrl+C after any option change. From owner-freebsd-ports@freebsd.org Mon Oct 2 10:05:39 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78434E3B695 for ; Mon, 2 Oct 2017 10:05:39 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37F7A270F for ; Mon, 2 Oct 2017 10:05:38 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id C0572A86B; Mon, 2 Oct 2017 12:05:36 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 7A86AA867 for ; Mon, 2 Oct 2017 12:05:36 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 02 Oct 2017 12:05:36 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> <436be05816210d94197b4171118ab029@acheronmedia.com> <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:05:39 -0000 On 2017-10-02 11:57, abi wrote: > 2. Dependency chain is not updated - if I disable B feature on port A, > poudriere asks me for options of ports implementing B. I have to > Ctrl+C after any option change. I find that annoying as well, but.... isn't that just how the config-recursive ports framework target works? Poudriere is really using the ports make targets here. Do synth or portmaster do it differently? -- Vlad K. From owner-freebsd-ports@freebsd.org Mon Oct 2 10:06:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5895E3B75B for ; Mon, 2 Oct 2017 10:06:59 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from lb3-smtp-cloud9.xs4all.net (lb3-smtp-cloud9.xs4all.net [194.109.24.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.xs4all.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 811212838 for ; Mon, 2 Oct 2017 10:06:59 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan ([83.160.85.125]) by smtp-cloud9.xs4all.net with ESMTP id yxbgdPYWEnIXbyxbhd8tMh; Mon, 02 Oct 2017 12:05:49 +0200 Received: from yokozuna (yokozuna [IPv6:0:0:0:0:0:0:0:1]) by yokozuna.lan (8.15.2/8.15.2) with ESMTPS id v92A5k7E019184 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Oct 2017 12:05:47 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Date: Mon, 2 Oct 2017 12:05:46 +0200 (CEST) From: Marco Beishuizen Sender: marco@yokozuna.lan Reply-To: Marco Beishuizen To: "Matthew D. Fuller" cc: Thomas Mueller , freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? In-Reply-To: <20171002004919.GL53186@over-yonder.net> Message-ID: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <201709290909.v8T99QtU006095@mxdrop301.xs4all.net> <20171002004919.GL53186@over-yonder.net> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-CMAE-Envelope: MS4wfBTeah5OA4iypFBlMaZ343qM24/CzfimvrOg7LxXLpEjpjL8hNyZFmU1W6z7MJMQmWXAJFkIjojS7Lejvx5rbmmGoOB+CtXLtLVa45P+6K/ERnF6ehXb oLO8s39Iyi9cgnxqpGr9NSd5N24AUOAVsZflAUJ0zqFdyL0Spqmvoabdi8Di8euxDPp/Jq+yLNTLBYF07i+LjAyKTH7YFKzIgwI2/ZEShnHMHTQeQ553V+hu z/V1aIcLAfuUKF7OmZ8DSQ== X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:07:00 -0000 On Mon, 2 Oct 2017, the wise Matthew D. Fuller wrote: > On Fri, Sep 29, 2017 at 09:21:31PM +0200 I heard the voice of Marco > Beishuizen, and lo! it spake thus: >> >> Using portupgrade every day and still works great. Tried portmaster >> once but liked portupgrade more. I use poudriere just for testing >> ports. > > I also use portupgrade constantly on several systems, and portmaster > occasionally for some special cases where it has advantages. > > I also use poudriere on a lot of systems. Actually, most, nowadays. And > I'm extremely happy with it. But I expect the systems I'm running > straight out of ports now will continue to do so for a very long time, > since poudriere just won't fit at all. I agree, imho poudriere is designed to maintain ports and testing them, or if you have to build ports for lots of systems. And it works very well for that too. But portupgrade and portmaster are imho far better in just tracking newer versions of installed ports. I'm also not sure if poudriere is able to track ports on a STABLE system (as in my case). So I hope both tools will be available in the future. -- Breeding rabbits is a hare raising experience. From owner-freebsd-ports@freebsd.org Mon Oct 2 10:25:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4993BE3BD5D for ; Mon, 2 Oct 2017 10:25:43 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE7E0302F for ; Mon, 2 Oct 2017 10:25:42 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id u5so3358694wrc.5 for ; Mon, 02 Oct 2017 03:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2hjobNzJkcG7vROrF39VUGrSnzqh6PqncuqDnqQGE5g=; b=OHNdh8itngs9PJYGvIy0WQCDXkC/Fr33jEynMLEodBW5VIknk5SRiC0bFTn6sqP2O2 GXbnq5s4O5jO2WRddzLStuaA7z7mUB7jg/xDyh7RzlYTeZbRh8CufEJp4mAhQFqHnBoV qE3r7G7kFZNhoBPzGgzAQYor+xBBlq4wTphcrbfTRcTq/gnsvnA6kI/qZZGo9+TBlbtk ox03lEv47dPtXek77f9OHqt4BEfuutSFve9U1bipeSavP4RgULobE7fySwwGeODxBwx3 GiVDfzKi7t8eDqv+pcT9FEyaOY1s1i0RrlJWfGskYDVy13HsJu07jlVWwT+caUINGEhr Urtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=2hjobNzJkcG7vROrF39VUGrSnzqh6PqncuqDnqQGE5g=; b=PR1JLIcgsRfKB34dCurDES11QJtba0lFk13jXLvH/0f8U6CXQGZoZn34dMLGtKudMi riaXVN4UmZJKw/l16b49YrXP/GFKy67OiiVVuVIE1e2phGyBcmF88whwiGB3pDcp0Hcu hc3xamk8WpmySPa5TLy6UT9ZMCCmcEkfS3BcXjm3++kOthjMcL815Y5eZK26WiYlLoBt LFQS4iw4Vx88lj30nQ+ujFBd2wgQHV783/XGeYMt7L2hxvM6BZxH3nbPm5tiEyP0zcTC ftQe/NAv2HUEjidSyk/+E1Kldme9wXHu2LUoGDdITYauHllEXKyj6EHQ1rJuTK/206gC wT6g== X-Gm-Message-State: AHPjjUiHVe1EcCvrOy3mX1t1kKWIb7pqvFDV+I2uq0PU+gGL10WCdfC8 g+7Hv41r8PA/YOYgel1ZXrePSN4y X-Google-Smtp-Source: AOwi7QA8PTytjAEXR2WPDyg+wXplY77nAMZVTyD3cdwAganrRYOm++hEDoRO8DR2gIMbtNzk5npLFA== X-Received: by 10.223.198.130 with SMTP id j2mr14912039wrg.52.1506939941347; Mon, 02 Oct 2017 03:25:41 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id u96sm13977535wrc.68.2017.10.02.03.25.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Oct 2017 03:25:40 -0700 (PDT) Date: Mon, 2 Oct 2017 11:25:38 +0100 From: Matt Smith To: "Vlad K." Cc: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002102538.GB48518@gmail.com> Mail-Followup-To: Matt Smith , "Vlad K." , freebsd-ports@freebsd.org References: <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> <436be05816210d94197b4171118ab029@acheronmedia.com> <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:25:43 -0000 On Oct 02 12:05, Vlad K. wrote: >On 2017-10-02 11:57, abi wrote: >>2. Dependency chain is not updated - if I disable B feature on port A, >>poudriere asks me for options of ports implementing B. I have to >>Ctrl+C after any option change. > > >I find that annoying as well, but.... isn't that just how the >config-recursive ports framework target works? Poudriere is really >using the ports make targets here. > >Do synth or portmaster do it differently? > Synths philosophy was that you should have the absolute bare minimum of options set and John wrote a script to do just this in /usr/ports/Tools/scripts/redundant-opt-files.sh to delete any which just have defaults in them. My method with poudriere is to maintain two files, pkglist which is the list of ports that I want to bulk build, and optlist which is the list of ports for which I don't want the default options. This one is a hugely cut down list. I then occasionally run poudriere options -n -j jailname -f optlist so that it non-recursively only gives me a dialog for the ports with non-default options. -- Matt From owner-freebsd-ports@freebsd.org Mon Oct 2 10:28:06 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A1E8E3BDD1 for ; Mon, 2 Oct 2017 10:28:06 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC9F30F6 for ; Mon, 2 Oct 2017 10:28:04 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id 615AEA8FF; Mon, 2 Oct 2017 12:27:57 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id E67CAA8FB for ; Mon, 2 Oct 2017 12:27:56 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 02 Oct 2017 12:27:56 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Organization: Acheron Media In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <201709290909.v8T99QtU006095@mxdrop301.xs4all.net> <20171002004919.GL53186@over-yonder.net> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.6 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:28:06 -0000 On 2017-10-02 12:05, Marco Beishuizen wrote: > > I agree, imho poudriere is designed to maintain ports and testing > them, or if you have to build ports for lots of systems. And it works > very well for that too. But portupgrade and portmaster are imho far > better in just tracking newer versions of installed ports. I'm also > not sure if poudriere is able to track ports on a STABLE system (as in > my case). It may've been the original design idea, but Poudriere is the de facto pkg building tool on FreeBSD for the official pkg repository, so its application is far from just testing. Also, Poudriere is building a repository, comparing it to any other tool for tracking _installed_ ports is simply wrong, pkg does that. Even with portmaster, pkg does that as portmaster builds a pkg and registers it with the pkg database. It will perfectly detect changes and upgrade newer versions of packages for the repos it is maintaining, and `pkg upgrade` will handle the tracking of installed packages. There is also huge advantage in building a repo FIRST, then using pkg LATER. I've had a ton of issues upgrading ports that were in use, where a dependency would be upgraded first and the program in use would fail because its port is not yet updated for that change. So if we want to compare apples to apples, then the difference is between "simple" tools that directly manage files on the system, versus tools that prepare a pkg repo first, and you manage the files on the system with pkg (some-tool build-and-install vs some-tool build && pkg install). It may be someone's PREFERENCE to do the former, but there is no objective benefit of that over preparing pkgs first, in an (automatically managed) isolated environment. That said, Poudriere is perfectly capable to manage software on a single machine. It works out of the box with a few simple steps needed to set it up for that task (poudriere jail + poudriere ports). -- Vlad K. From owner-freebsd-ports@freebsd.org Mon Oct 2 10:39:44 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC912E3C019 for ; Mon, 2 Oct 2017 10:39:44 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF3C3549 for ; Mon, 2 Oct 2017 10:39:44 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 6ACCD5543 for ; Mon, 2 Oct 2017 10:39:41 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> <436be05816210d94197b4171118ab029@acheronmedia.com> <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> <20171002102538.GB48518@gmail.com> From: abi Message-ID: Date: Mon, 2 Oct 2017 13:38:57 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171002102538.GB48518@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506940781; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=LWS0hRuVzRVXEpvp32Gix13DgG7rc6zFoOB4hrkvFPc=; b=coWn1f15Vper5AYhd8KmsJr4F86fa4TxdZbxFZOl9pLtLjM3HxipLSGzVBZ7tpazTeu6F+ I5QCnJoO3/nK6kZGD2GepzH65dUGTGTInum44Kex7ZDYo5V+i1xu75Oo4O2S0zNvgWS+2Y gKwQxbax1l9PkLHVcG4Z0zaCi6wMoe0= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:39:45 -0000 02.10.2017 13:25, Matt Smith пишет: > On Oct 02 12:05, Vlad K. wrote: >> On 2017-10-02 11:57, abi wrote: >>> 2. Dependency chain is not updated - if I disable B feature on port A, >>> poudriere asks me for options of ports implementing B. I have to >>> Ctrl+C after any option change. >> >> >> I find that annoying as well, but.... isn't that just how the >> config-recursive ports framework target works? Poudriere is really >> using the ports make targets here. >> >> Do synth or portmaster do it differently? >> > > Synths philosophy was that you should have the absolute bare minimum > of options set and John wrote a script to do just this in > /usr/ports/Tools/scripts/redundant-opt-files.sh to delete any which > just have defaults in them. > The thing John doesn't explain why we need to purge "redundant options". They are not redundant, they inform user that port options are not changed after ports tree update. Synth softly suggests user *not* to change ports options, because it's hard to manage them and stay in synth "philosophy". From owner-freebsd-ports@freebsd.org Mon Oct 2 10:41:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89CBDE3C1BC for ; Mon, 2 Oct 2017 10:41:49 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id 36BE836F9 for ; Mon, 2 Oct 2017 10:41:49 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 441ED5555 for ; Mon, 2 Oct 2017 10:41:47 +0000 (UTC) Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <77738e54-16a9-8be9-0459-e2ca5cc837e5@abinet.ru> <436be05816210d94197b4171118ab029@acheronmedia.com> <94c5fbf8-414d-7fc7-3611-76f03f4e7d7d@abinet.ru> From: abi Message-ID: <9ed238bb-cdd8-922c-35c2-75f524a50814@abinet.ru> Date: Mon, 2 Oct 2017 13:41:03 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1506940907; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=ppqWalphGD+WaYeekSIxjArGxC6UwBHP4x41t5XcSfg=; b=Lp9FnS2I2QBfW8HKsWtZVppzZiFcY4UE9I4pwaBbNn/0vCSa6c1Bk0bNBwnT+Miznh9oCI +zEFHVZHZSt455XQzJDvMPWJhHFSa6c6+Hz2UUNynQcjBvSeKtyq9js5eh+XkrpiRofq+t 5xSiek9sumpSF4fytL+pAQoV9kMx+qs= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 10:41:49 -0000 02.10.2017 13:05, Vlad K. пишет: > On 2017-10-02 11:57, abi wrote: >> 2. Dependency chain is not updated - if I disable B feature on port A, >> poudriere asks me for options of ports implementing B. I have to >> Ctrl+C after any option change. > > > I find that annoying as well, but.... isn't that just how the > config-recursive ports framework target works? Poudriere is really > using the ports make targets here. > > Do synth or portmaster do it differently? > > portmaster has special handling for that - after dialog4ports invocation, it updates dependency chain of edited port with applied options and proceeds with real dependencies only. The thing poudrere could borrow, from my point of view. synth doesn't have tools to edit options, it reads only. From owner-freebsd-ports@freebsd.org Mon Oct 2 14:20:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2117E4062A for ; Mon, 2 Oct 2017 14:20:18 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id BBCDA6A0D1 for ; Mon, 2 Oct 2017 14:20:18 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B7EC1E40629; Mon, 2 Oct 2017 14:20:18 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B785AE40628 for ; Mon, 2 Oct 2017 14:20:18 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 91A0B6A0D0 for ; Mon, 2 Oct 2017 14:20:17 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-144-79.dyn.iinet.net.au [106.68.144.79]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v92EK0Uf033263 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Oct 2017 07:20:03 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: gettng the port revision number associated with the pkg repo. To: Lowell Gilbert Cc: "ports@FreeBSD.org" References: <27a74475-e146-0cd4-e5ac-f59686317be9@freebsd.org> <44fub9d054.fsf@be-well.ilk.org> <66ef45c6-b448-c8fe-9686-10f0cab13ecb@freebsd.org> <447ewjarab.fsf@be-well.ilk.org> From: Julian Elischer Message-ID: <60b690b5-d34d-56ea-a371-414d4dddaaaa@freebsd.org> Date: Mon, 2 Oct 2017 22:19:54 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <447ewjarab.fsf@be-well.ilk.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 14:20:18 -0000 On 28/9/17 9:25 pm, Lowell Gilbert wrote: > Julian Elischer writes: > >> On 26/9/17 10:07 pm, Lowell Gilbert wrote: >>> Julian Elischer writes: >>> >>>> SO imagine that I needed to be ab;e to reproduce the pkg repo as of a >>>> articular day, is there anywhere one can look to see the svn revision >>>> number that corresponds to teh current pkg files. >>>> >>>> >>>> I would like to take a snapshot at a particular revision.. but how do >>>> I find out what the revision was when the build was kicked off? >>> If you want to do that after the fact, I'm not sure how you'd specify >>> when you want the information for. But if you do it when you kick off >>> the build (or if you haven't changed the tree since), svnversion(1) >>> will tell you. >>> >> I mean for the official pkg repo.. >> >> is there a file somewhere that says "these packages are as of r443234"? > Sorry that I misunderstood your intent. > > I am fairly sure that what you want exists somewhere, but I can't find > it at the moment. > Unfortunately neither can I. From owner-freebsd-ports@freebsd.org Mon Oct 2 15:21:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B11D6E417B4 for ; Mon, 2 Oct 2017 15:21:59 +0000 (UTC) (envelope-from katelyn.pierce@infmicrohub.info) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 72E3C6BE2D for ; Mon, 2 Oct 2017 15:21:59 +0000 (UTC) (envelope-from katelyn.pierce@infmicrohub.info) Received: by mailman.ysv.freebsd.org (Postfix) id 6F400E417B3; Mon, 2 Oct 2017 15:21:59 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DB1FE417B2 for ; Mon, 2 Oct 2017 15:21:59 +0000 (UTC) (envelope-from katelyn.pierce@infmicrohub.info) Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0112.outbound.protection.outlook.com [104.47.100.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C45FB6BE27 for ; Mon, 2 Oct 2017 15:21:57 +0000 (UTC) (envelope-from katelyn.pierce@infmicrohub.info) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT1306907a.onmicrosoft.com; s=selector1-infmicrohub-info; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CfNJM2xS/RkTxwqE+ziZXIomM5le2GddhyjbRudQpnU=; b=ZXezGTtNnw8iDiDF0YLPaWeBUyDnbrRz12qxzmiREKKDy3eMmX7eRs8C2ZA6UBgE+nfl77P9rxcDFH+PSRkk9XftLuHjiVJ0TTi6GYsKH2VxmDLdZWNF84UswicIG7kVYEGD6t236ESwudDTSthzjBrHSFPAHIycnPE78iv41Nk= Received: from MA1PR01MB0504.INDPRD01.PROD.OUTLOOK.COM (10.164.121.146) by MA1PR01MB0504.INDPRD01.PROD.OUTLOOK.COM (10.164.121.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Mon, 2 Oct 2017 15:21:54 +0000 Received: from MA1PR01MB0504.INDPRD01.PROD.OUTLOOK.COM ([10.164.121.146]) by MA1PR01MB0504.INDPRD01.PROD.OUTLOOK.COM ([10.164.121.146]) with mapi id 15.20.0077.018; Mon, 2 Oct 2017 15:21:53 +0000 From: Katelyn Pierce To: "ports@freebsd.org" Subject: Multiprotocol Label Switching Thread-Topic: Multiprotocol Label Switching Thread-Index: AdM7kVMrf+t6vLzfRuiwPnTA6lUbQQ== Date: Mon, 2 Oct 2017 15:18:27 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=katelyn.pierce@infmicrohub.info; x-originating-ip: [49.207.51.177] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; MA1PR01MB0504; 6:+9Iw2FVCf2D9kmjQkCfXmiVZyiTO5pcRvHSItX68pds8NoMV4HoL2BBfYA4Kgf6mjB6l2kPROyD0V+BaBjRJiL5nDTxa1DTUNTpcS1lhcDXY6HEviHpIlr6Wt8SDZCi6ypfgGZ9K6/ccVXFujeoQ+fIXDdi6OOnc+2pPY6oZY84V+idBkwUnDsYyLCDOP88ekDzkCLDoL9JLTV8gHro42qoPx+V7bgRbDKEKOeNqwJ1HXsGiqUIKGtarlWlrrT/v2ks0apZUqovWfHMi4j8RY4ibiNa9BQjVdLusGj2zj6w0LkhL622mY7ud0wW9myPyGFndA/uVfgE1b6dhzffJNg==; 5:vHxapS5bdwwL4c8Y+FX2SLKu/MJc8yZTwjGcnxhRiCzY9VbjZsKFAUQKrpuyi7qjwNg3RVrZuF/9pjOBzBjnTIcodyngtIVsJpX2j0d7D5JrBAgCxGiM7YU8PYDsT8pQCxwefEsolx4351GlfOiDfQ==; 24:T14y6fgZ90Ed6Gw78Zrz4KtkErwZTjWcOqiANfwh3/tnmN8MExIzbbqxVCvNzO51zfSMpCRSns+WtaQ8qC8IIFhH07D99YeG1WENQ6aQRqI=; 7:IPYDt4lJuefAf/fWjeUD/KLQHSEmM8D8Ynhq693QQH8f2r1B1080AnKC0GhABbp29Yz1KNSOLq6LOZDTu8vyXWDlpP5PrJUnkxrdVm+xvOdqf4B31Ye4gO9V770FCakzPRiHjT0GMUIZLdvnqvQjVY3WlvU8yuNo+lntIvzZH4orcrTRInWYpycUKCOgnx0NOE3Kz9d0V8lM3vsl0oJWYsry2AZyA2TEpp77SlXgYMs= x-ms-office365-filtering-correlation-id: 980c68e9-2166-45bd-e528-08d509a94ff8 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017082002075)(2017052603199)(201703131423075)(201702281549075)(201702085555020)(201702085554020)(201702085553020)(201702085551020); SRVR:MA1PR01MB0504; x-ms-traffictypediagnostic: MA1PR01MB0504: x-exchange-antispam-report-test: UriScan:(21748063052155); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6041248)(20161123555025)(20161123564025)(20161123560025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(2016111802025)(6043046)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:MA1PR01MB0504; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:MA1PR01MB0504; x-forefront-prvs: 0448A97BF2 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(199003)(189002)(6666003)(33656002)(74316002)(2351001)(7116003)(3480700004)(5660300001)(478600001)(7736002)(790700001)(3846002)(189998001)(6116002)(102836003)(7520500002)(626008)(2501003)(316002)(53936002)(106356001)(105586002)(97736004)(3660700001)(86362001)(8676002)(1730700003)(81156014)(3280700002)(81166006)(55016002)(7696004)(77096006)(2906002)(68736007)(101416001)(66066001)(8936002)(14454004)(6436002)(25786009)(2900100001)(6506006)(5630700001)(6916009)(6306002)(50986999)(5640700003)(54896002)(54356999)(9686003)(45842010); DIR:OUT; SFP:1102; SCL:1; SRVR:MA1PR01MB0504; H:MA1PR01MB0504.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: infmicrohub.info does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: infmicrohub.info X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2017 15:18:27.2338 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: b6359ec1-e8fb-45ff-9edb-be159fa53ccc X-MS-Exchange-Transport-CrossTenantHeadersStamped: MA1PR01MB0504 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 15:21:59 -0000 Hello there, I would like to know if you are interested in acquiring a list of companies= using Multiprotocol Label Switching. Information fields: Names, Title, Email, Phone, Company Name, Company URL, = Company physical address, SIC Code, Industry and Company Size (Revenue and = Employee). Let me know if you are interested and I will get back to you with the count= s, sample and pricing. Regards, Katelyn Pierce Marketing Executive To opt out, please reply with Leave Out in the Subject Line. From owner-freebsd-ports@freebsd.org Mon Oct 2 16:21:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95D6AE0DBEC; Mon, 2 Oct 2017 16:21:51 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 192F76DC35; Mon, 2 Oct 2017 16:21:51 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id d10so4335033lfg.11; Mon, 02 Oct 2017 09:21:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JP8SubLyrPRqjKl4JSoKO2r5XcgUzddXNgPNojpchvQ=; b=aj91hEafe8N1gpGJpq6FTM7+5XX28pQDKEkptgcbdjtzJuZVCfgCmWtY8biO1tSULf iHriKfqrhow7xpwty7xu6E8gnACYJ++J6rFV5uDV/gHjuGruxPRFWwGeGOBNfkxr9tuL MiU9seZZwIbAJMSC/M1kzoK8qLx+3zWbnDX9fs+enuE6f5J3/zIF8VtCEAHQCXSPW7Ib UHsK8Q1agK4O7ClkqZxBM3OB060VfAhtiN70EjADFYjszLvCDtPI139NABBEsSVdj4ey dN1o58Pr+TNfka+n++SZ2H5M/nH40QxcIrsGtl5cqMN4J9SjQDyp76ZwwCnEvCsdZAwS pi4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JP8SubLyrPRqjKl4JSoKO2r5XcgUzddXNgPNojpchvQ=; b=bzLCVi8fNjIkEjMTKZ4WfLR+oRYsa2aIS/3GVFOz+qria/MREN6BAVJFCmjVwTLg6G 05Z2tHLTybVgkA7gZlmBQG9Gbr6wqGhoN8ORH4b4uHBIkhTlrtcOMGg3OjVuL5b8V221 6BsbneevfFMp1mapBCwPabuKQVQ6biy2Md5SOQeFQl8xFzmw6GjOhYqPVfZUMvcWZPxF OhGzCLiw2gJHQ9CfOrwSJT0c5L9GJBI3wTaQDLBqP4b4y2dCwVPrOlCwWaxX9owOXgCD HZZAJdr7XL9456iSDpdiz5DVVP1WYk/tvN7YZfHCoVm0gRiWlteEeO7/DcGGweiK6V4E Luaw== X-Gm-Message-State: AHPjjUjNt6Sb2mLX4CwjAWLGW5Cuu+07tcgLzDe6jMMQy6yUllovzvVJ msTVFua8oswn/ExJ21w76cXZ+ksJHVbS0NCMSf8= X-Google-Smtp-Source: AOwi7QC0nRnB17Mk6BXfbzaBECRxx179JlzWj7Z2NAHfDs5nN4bKkIZGT8mNa7q1hKOv8N19EmUuerKCoUOxxgqiFTk= X-Received: by 10.46.101.24 with SMTP id z24mr7150513ljb.42.1506961309260; Mon, 02 Oct 2017 09:21:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.14.2 with HTTP; Mon, 2 Oct 2017 09:21:48 -0700 (PDT) In-Reply-To: References: <8a3e663a-d94f-0ef7-bbc7-8ebaa111f6dd@FreeBSD.org> <7b2f2464-5c35-e24a-2047-838c1a9e96a3@FreeBSD.org> From: Russell Haley Date: Mon, 2 Oct 2017 09:21:48 -0700 Message-ID: Subject: Re: Porters Handbook section 4.4 To: Warren Block Cc: koobs@freebsd.org, doc@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 16:21:51 -0000 On Fri, Sep 29, 2017 at 7:58 AM, Warren Block wrote: > On Mon, 25 Sep 2017, Russell Haley wrote: > >> Thanks! I'll play with this on the weekend. > > > Please create a review at https://reviews.freebsd.org/ and add me as a > reviewer. > > Thanks! Will do. Just a progress update: I got the handbook sources and found the section in chapter.xml. I created a Geany project with everyone's raw notes and the sources. To be continued... Russ From owner-freebsd-ports@freebsd.org Mon Oct 2 16:25:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43DE8E0DDB1 for ; Mon, 2 Oct 2017 16:25:48 +0000 (UTC) (envelope-from simon.wright@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C29D6E028 for ; Mon, 2 Oct 2017 16:25:46 +0000 (UTC) (envelope-from simon.wright@gmx.net) Received: from [192.168.79.177] ([112.198.72.124]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MYKGj-1dm30Q3dj7-00V5sA for ; Mon, 02 Oct 2017 18:25:44 +0200 Subject: Re: gettng the port revision number associated with the pkg repo. To: freebsd-ports@freebsd.org References: <27a74475-e146-0cd4-e5ac-f59686317be9@freebsd.org> <44fub9d054.fsf@be-well.ilk.org> <66ef45c6-b448-c8fe-9686-10f0cab13ecb@freebsd.org> <447ewjarab.fsf@be-well.ilk.org> <60b690b5-d34d-56ea-a371-414d4dddaaaa@freebsd.org> From: Simon Wright Message-ID: Date: Tue, 3 Oct 2017 00:25:40 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <60b690b5-d34d-56ea-a371-414d4dddaaaa@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:0A0l5Pb8y77iC3cMG7LqoxQuTyLRUUVhvI0VLNO6VXg1PVXbERr V/snmDAwSmhc061ayFJ1IKZ/H682GU4jsCYT+TlFmgEK39OTrYcrc3yioW/Qv3qUmMs6ClK Wq0tAPJykzbzIN75sZjwPd64G/ou+7XT04IX42rXdGHCsom5ObkyyStg9/yNarJEfmoIiVj tgTOZ6BKilg2tsdc2KNvg== X-UI-Out-Filterresults: notjunk:1;V01:K0:+HHbgFZZE0w=:1ShT4gB30MMCFi0RoXdWS2 +7gyGIOLIxttR1hqzL6DghH7kYDAmv2srZDIOrbGdgSSvnSM2HTdMGiZipLtAD9AdcBbEE+ZD nwPjmCbL4RaVMCmJPEheWhEvhohXh+JPmOHR0YW9U8Uo5IwD7KCNkXsPqt9hPcBzMfETM/STm fnEQaDDAcf/1xx2MbcdIKukKNmUTgdmnpD4z5JA9WN3ssmsUIq3OL/oCPTVo27JffMOAAaxN1 WYHeuJsCC5EBkB8Dz/B4J1ATC18Plc+gGKaKYuh45//n2fHJCHqKUshmluTGdfcvbcWYoldrY B6hbrt1wA+DTRKAS0/X6BiKDCeHvSA/sZYh6IISMiiv8FDxC4TBOxuE7pHD+b82CGT1V5RRYY 6Q5E2Q+OZ8p0FmBF/dtOyAGfXp91zrM2bR4/7Pyg2C/2jlMRJg47swW+2y6cd83iNhiFwQwki QhfqOzqzlD5mwaH8jh3pVLBwhg6PGXtCe29hCqF8OuwlagnEBmJ2a9564uIjoWEDGdwhQm5+0 Oz+7yBJEigOMLl9nFOTBWrJniQla0IQuGu8oTnL2DXhdzpVPe2+uJqqflVdkRvtEGmjTfcuNR +bN8R0y09vWvoX1MJ2be0Tjg4j+fKPk7cV8MKQ6Lm3wOvc05QFFUQ7PCV7+pKZ7mNeqh48oxg CgxXzcJJh7cU8hbP/bkriL5DEOspWkk8vnLPE66okTQ6KeJrZpvVhLKWJEg7NW4XrqIMCGAJb Qg6wMCBnlHUKkgUFMHLpUWK5Zjwe07DXHxKN2C2BJ+wuD3E4kuKgv1A9WeiXo3aqzdjfTWP9R a8evkWpUYJsnZcuWaJTfi6tsgdxt5uQI09grex+Uu7xtUlSpfYfpW/o9T7NxeJpsXkbok7W X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 16:25:48 -0000 On 02/10/2017 22:19, Julian Elischer wrote: > On 28/9/17 9:25 pm, Lowell Gilbert wrote: >> Julian Elischer writes: >> >>> On 26/9/17 10:07 pm, Lowell Gilbert wrote: >>>> Julian Elischer writes: >>>> >>>>> SO imagine that I needed to be ab;e to reproduce the pkg repo >>>>> as of a >>>>> articular day, is there anywhere one can look to see the svn >>>>> revision >>>>> number that corresponds to teh current pkg files. >>>>> >>>>> >>>>> I would like to take a snapshot at a particular revision.. but >>>>> how do >>>>> I find out what the revision was when the build was kicked off? >>>> If you want to do that after the fact, I'm not sure how you'd >>>> specify >>>> when you want the information for. But if you do it when you >>>> kick off >>>> the build (or if you haven't changed the tree since), svnversion(1) >>>> will tell you. >>>> >>> I mean for the official pkg repo.. >>> >>> is there a file somewhere that says "these packages are as of >>> r443234"? >> Sorry that I misunderstood your intent. >> >> I am fairly sure that what you want exists somewhere, but I can't >> find >> it at the moment. >> > Unfortunately neither can I. Hi Julian, Lowell I need this information so that I can start my poudriere builds with my quite small list of ports with non-standard options from the same revision as the pkg system. I use a somewhat modified version of this script: https://gist.github.com/reedacartwright/8622973baf89b263a6d7 Thanks to Reed for creating and maintaining this. -- Simon. From owner-freebsd-ports@freebsd.org Mon Oct 2 16:40:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71EDBE0E30D for ; Mon, 2 Oct 2017 16:40:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 556736E811 for ; Mon, 2 Oct 2017 16:40:25 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v92GiKim079670 for ; Mon, 2 Oct 2017 09:44:26 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20171002092849.GA48518@gmail.com> References: <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> , <20171002092849.GA48518@gmail.com> From: "Chris H" Subject: Re: Status of portupgrade and portmaster? Date: Mon, 02 Oct 2017 09:44:26 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 16:40:26 -0000 On Mon, 2 Oct 2017 10:28:49 +0100 Matt Smith wrote > On Oct 02 09:07, Carmel NY wrote: > >On Sun, 1 Oct 2017 23:49:14 +0100, Matthew Seaman stated: > > > >>On 01/10/2017 11:34, Carmel NY wrote: > >>> 1. Does it determine out-of-date update packages automatically or does > >>> the user have to determine that what is out-of-date and feed them to > >>> poudriere manually and in the proper order? > >> > >>Automatic. > >> > >>> 2. From what I have read, the user is required to install each package > >>> manually. Is that correct? > >> > >>Poudriere builds a repository. You then have to type 'pkg upgrade' or > >>'pkg install foo' to update your live system. Most people do not find > >>this particularly taxing. > > > >From the "pkg-descr" file: > > > >poudriere is a tool primarily designed to test package production on > >FreeBSD. However, most people will find it useful to bulk build ports > >for FreeBSD. > > > >While it will undoubtedly work, it is still more complex than the average > >desktop user requirers. Synth fits the bill nicely by being, for the most > >part, easy to understand and run. I am already on my forth "ports > >maintenance" program having used portmanager, portmaster, portupgrade and > >now synth. At this point, I would almost rather switch to a new OS before > >abandoning synth for something that IMHO is just overkill for the average > >user. > >Just my 2¢. > > > > Of course if you did move to a different OS then the chances are you > would be using a binary package repository and not compiling any > software from source. So you wouldn't have any choice over the options > that these packages were built with. > > If you are happy enough to do this then you may as well just abandon > building ports on FreeBSD anyway and just use the pkg tool from the > official FreeBSD repository. This is the easiest option surely. > > For what it's worth I've used both synth and poudriere and whilst > poudriere is slightly heavier to use because of the requirement to > create a build jail first, once that step has been done it's pretty much > identical to using synth really. > > My workflow is simply this: > > poudriere ports -u (update the ports tree) > poudriere bulk -j 11 -f pkglist (check for any updates and build any > packages listed in the pkglist file) > pkg upgrade (upgrade any upgraded packages) > > That's it. The same workflow on synth is: > svn up /usr/ports > synth build pkglist > pkg upgrade > > Pretty similar if you ask me. OK you could use synth upgrade-system and > do it in one command rather than two but then you're building everything > on the host system and not a specific list. Also I like the extra pkg > stage, it gives me a chance to see what pkg is about to do and abort it > if it wants to do something insane. I think you really made the point here, Matt; IMHO It's really a Chocolate vs Vanilla, Broccoli vs Corn situation. Both are fine; but not everyone is willing to have/choose either, and someone(TM) is going to have to step up, and ensure that *both* are available, before both parties are going to be satisfied/happy. :) Just the way I see it (my .02¢) So. Has John paid the necessary penance yet? ;) ;) --Chris > > -- > Matt > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Oct 2 17:12:58 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0984E0EEC3 for ; Mon, 2 Oct 2017 17:12:58 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 78C0A6F75A for ; Mon, 2 Oct 2017 17:12:58 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v92HCmdW033734; Mon, 2 Oct 2017 10:12:52 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201710021712.v92HCmdW033734@gw.catspoiler.org> Date: Mon, 2 Oct 2017 10:12:48 -0700 (PDT) From: Don Lewis Subject: Re: Status of portupgrade and portmaster? To: mbeis@xs4all.nl cc: fullermd@over-yonder.net, mueller6722@twc.com, freebsd-ports@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 17:12:58 -0000 On 2 Oct, Marco Beishuizen wrote: > I'm also not sure if poudriere > is able to track ports on a STABLE system (as in my case). Yes it can. If you use the svn method when creating a jail you can chose any arbitrary source branch from the svn repository and then you can specify any desired svn revision on that branch when you update the jail. You would probably want to use this method when building ports for 12.0-CURRENT rather than creating the jail using a 12.0-CURRENT snapshot. From owner-freebsd-ports@freebsd.org Mon Oct 2 17:29:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 636CBE0F4DC for ; Mon, 2 Oct 2017 17:29:35 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 256C36FF72 for ; Mon, 2 Oct 2017 17:29:34 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-144-79.dyn.iinet.net.au [106.68.144.79]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v92HTTo3033905 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Oct 2017 10:29:32 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: gettng the port revision number associated with the pkg repo. [Please?) To: Simon Wright , freebsd-ports@freebsd.org References: <27a74475-e146-0cd4-e5ac-f59686317be9@freebsd.org> <44fub9d054.fsf@be-well.ilk.org> <66ef45c6-b448-c8fe-9686-10f0cab13ecb@freebsd.org> <447ewjarab.fsf@be-well.ilk.org> <60b690b5-d34d-56ea-a371-414d4dddaaaa@freebsd.org> From: Julian Elischer Message-ID: Date: Tue, 3 Oct 2017 01:29:23 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 17:29:35 -0000 On 3/10/17 12:25 am, Simon Wright wrote: > On 02/10/2017 22:19, Julian Elischer wrote: >> On 28/9/17 9:25 pm, Lowell Gilbert wrote: >>> Julian Elischer writes: >>> >>>> On 26/9/17 10:07 pm, Lowell Gilbert wrote: >>>>> Julian Elischer writes: >>>>> >>>>>> SO imagine that I needed to be ab;e to reproduce the pkg repo >>>>>> as of a >>>>>> articular day, is there anywhere one can look to see the svn >>>>>> revision >>>>>> number that corresponds to teh current pkg files. >>>>>> >>>>>> >>>>>> I would like to take a snapshot at a particular revision.. but >>>>>> how do >>>>>> I find out what the revision was when the build was kicked off? >>>>> If you want to do that after the fact, I'm not sure how you'd >>>>> specify >>>>> when you want the information for. But if you do it when you >>>>> kick off >>>>> the build (or if you haven't changed the tree since), svnversion(1) >>>>> will tell you. >>>>> >>>> I mean for the official pkg repo.. >>>> >>>> is there a file somewhere that says "these packages are as of >>>> r443234"? >>> Sorry that I misunderstood your intent. >>> >>> I am fairly sure that what you want exists somewhere, but I can't >>> find >>> it at the moment. >>> >> Unfortunately neither can I. > > Hi Julian, Lowell > > I need this information so that I can start my poudriere builds with > my quite small list of ports with non-standard options from the same > revision as the pkg system. I use a somewhat modified version of > this script: > > https://gist.github.com/reedacartwright/8622973baf89b263a6d7 > > Thanks to Reed for creating and maintaining this. > can we just find out who runs the poudriere instances and ask them to just append the svn revision number somewhere? or maybe even the poudriere commands  used.. *somewhere*? From owner-freebsd-ports@freebsd.org Mon Oct 2 17:36:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FD92E0F7FC for ; Mon, 2 Oct 2017 17:36:56 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB24C70389 for ; Mon, 2 Oct 2017 17:36:55 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v92HetJB089288 for ; Mon, 2 Oct 2017 10:41:01 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> , <20171002092849.GA48518@gmail.com>, From: "Chris H" Subject: Re: Status of portupgrade and portmaster? Date: Mon, 02 Oct 2017 10:41:01 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 17:36:56 -0000 On Mon, 02 Oct 2017 09:44:26 -0700 "Chris H" wrote > On Mon, 2 Oct 2017 10:28:49 +0100 Matt Smith wrote > > > On Oct 02 09:07, Carmel NY wrote: > > >On Sun, 1 Oct 2017 23:49:14 +0100, Matthew Seaman stated: > > > > > >>On 01/10/2017 11:34, Carmel NY wrote: > > >>> 1. Does it determine out-of-date update packages automatically or does > > >>> the user have to determine that what is out-of-date and feed them to > > >>> poudriere manually and in the proper order? > > >> > > >>Automatic. > > >> > > >>> 2. From what I have read, the user is required to install each package > > >>> manually. Is that correct? > > >> > > >>Poudriere builds a repository. You then have to type 'pkg upgrade' or > > >>'pkg install foo' to update your live system. Most people do not find > > >>this particularly taxing. > > > > > >From the "pkg-descr" file: > > > > > >poudriere is a tool primarily designed to test package production on > > >FreeBSD. However, most people will find it useful to bulk build ports > > >for FreeBSD. > > > > > >While it will undoubtedly work, it is still more complex than the average > > >desktop user requirers. Synth fits the bill nicely by being, for the most > > >part, easy to understand and run. I am already on my forth "ports > > >maintenance" program having used portmanager, portmaster, portupgrade and > > >now synth. At this point, I would almost rather switch to a new OS before > > >abandoning synth for something that IMHO is just overkill for the average > > >user. > > >Just my 2¢. > > > > > > > Of course if you did move to a different OS then the chances are you > > would be using a binary package repository and not compiling any > > software from source. So you wouldn't have any choice over the options > > that these packages were built with. > > > > If you are happy enough to do this then you may as well just abandon > > building ports on FreeBSD anyway and just use the pkg tool from the > > official FreeBSD repository. This is the easiest option surely. > > > > For what it's worth I've used both synth and poudriere and whilst > > poudriere is slightly heavier to use because of the requirement to > > create a build jail first, once that step has been done it's pretty much > > identical to using synth really. > > > > My workflow is simply this: > > > > poudriere ports -u (update the ports tree) > > poudriere bulk -j 11 -f pkglist (check for any updates and build any > > packages listed in the pkglist file) > > pkg upgrade (upgrade any upgraded packages) > > > > That's it. The same workflow on synth is: > > svn up /usr/ports > > synth build pkglist > > pkg upgrade > > > > Pretty similar if you ask me. OK you could use synth upgrade-system and > > do it in one command rather than two but then you're building everything > > on the host system and not a specific list. Also I like the extra pkg > > stage, it gives me a chance to see what pkg is about to do and abort it > > if it wants to do something insane. > I think you really made the point here, Matt; > IMHO It's really a Chocolate vs Vanilla, Broccoli vs Corn situation. > Both are fine; but not everyone is willing to have/choose either, and Ahem, s/either/both/g the above line should have read both, not either. sorry. :( > someone(TM) is going to have to step up, and ensure that *both* are > available, before both parties are going to be satisfied/happy. :) > > Just the way I see it (my .02¢) > > So. Has John paid the necessary penance yet? ;) ;) > > --Chris > > > > -- > > Matt > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Oct 2 18:02:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B70BE2303E for ; Mon, 2 Oct 2017 18:02:40 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from lb3-smtp-cloud8.xs4all.net (lb3-smtp-cloud8.xs4all.net [194.109.24.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.xs4all.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 97FE770F9A; Mon, 2 Oct 2017 18:02:38 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan ([83.160.85.125]) by smtp-cloud8.xs4all.net with ESMTP id z51ydrCvUg5cRz51zdzkAv; Mon, 02 Oct 2017 20:01:28 +0200 Received: from yokozuna (yokozuna [IPv6:0:0:0:0:0:0:0:1]) by yokozuna.lan (8.15.2/8.15.2) with ESMTPS id v92I1OZM072062 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Oct 2017 20:01:25 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Date: Mon, 2 Oct 2017 20:01:24 +0200 (CEST) From: Marco Beishuizen Sender: marco@yokozuna.lan Reply-To: Marco Beishuizen To: Don Lewis cc: mueller6722@twc.com, freebsd-ports@freebsd.org, fullermd@over-yonder.net Subject: Re: Status of portupgrade and portmaster? In-Reply-To: <201710021712.v92HCmdW033734@gw.catspoiler.org> Message-ID: References: <201710021712.v92HCmdW033734@gw.catspoiler.org> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-CMAE-Envelope: MS4wfJ1+tjX4lGS0Ip7Mk9LjXqadVgkKrshH/3uQdtduJMXmnvBEtYAQTnjeKxptK4NabPBevXHJmsy09Lj1/unfmHKopfrif1+4O9Zf54n6HQfcPu88Xxn9 hzGELhb/6/ciVCY0tTBy39MadCToOGbAfwsRg13oaYkWJQfQ/qVP9nZLwvCOBo+B+AtvOY6u/8ZJw7q9xWGfP3QL8hUz94vRsor4PrV9KD/t+V3zZ+swhP+d 6h2gY4cNCFo38iWM6HBCXfXmybVSIvrE9Y8S4t78tSE= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 18:02:40 -0000 On Mon, 2 Oct 2017, the wise Don Lewis wrote: > Yes it can. If you use the svn method when creating a jail you can > chose any arbitrary source branch from the svn repository and then you > can specify any desired svn revision on that branch when you update the > jail. You would probably want to use this method when building ports > for 12.0-CURRENT rather than creating the jail using a 12.0-CURRENT > snapshot. I'm running 11.1-STABLE now, upgrading every few months or when there is an important security fix. Do I have to build a new system twice in that case (once my running system and once the poudriere jail)? -- Science is facts; just as houses are made of stones, so is science made of facts; but a pile of stones is not a house and a collection of facts is not necessarily science. -- Jules Henri Poincar'e From owner-freebsd-ports@freebsd.org Mon Oct 2 18:09:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DF9BE23262 for ; Mon, 2 Oct 2017 18:09:36 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78FE071336; Mon, 2 Oct 2017 18:09:35 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id k4so10118181wmc.1; Mon, 02 Oct 2017 11:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=LtweEevTf3ZDrsmbMVuJm3qhSOE2gAq0JrVpkhrkbD8=; b=t3IHLwRxncXmdur4x4KjK/arfVwAxecD5ZeSHTf5mgUjT/Z0wcCxKmkHFL/c2K/5fa TDObN3+aIe4732KGhUgie1ZhiWk34X6hCpyw8BrdyEOcipc0WqN/EbZlK8SL1Seb35jf 8NhLJ9vZbj/tbTNSdm7HKAkTZ6YwqaG2wxk2Xp9Cgi8Ebs4jDZK0+abvmsPpVGhotYLU Rh9TNoHCT/3vTDemx6U5BgEjrj6M873TcJJRasQR/r3wh2Q37SJYYJ5R531cu4LaqJtU M3avo9WCtcNbER0jgulVZGs7X80ONSk2tZhNlEwpgx/eW9BRhwEoJGultCvYkRvsKByR ZDIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=LtweEevTf3ZDrsmbMVuJm3qhSOE2gAq0JrVpkhrkbD8=; b=ebeyoKCp+2OSmW/klL9zdTDdx/tlW1BUOVoc70/oF8V0g2a8zR7XPvDM7RFZwr/XgA 25sSQoQxE7kw60w3dkkhIZzwFKqoStf0Gu2TH2PZ4lQElpOKFYPlZuW3jk5Juc3PC2HH 50I2Fu3JqG7llEfFqhsF3+huV9TKTDRRBQWwBqwkaXL7/VGjRldtOiMEHOwjBnVuovwg n6L//tUpaL6mybg26PLANwyVxwNL06tMW0nu/iDCPH284UIuuQCw5haSXF1CFDhBh28k Ubw7JEQJhs0LKN71cofrCB5mk/ss4Auy2zGh5H7MvvoC8S+1ImMSWAJU7nbt1WaegT7Z QUUg== X-Gm-Message-State: AMCzsaVQBJhN/R/bbVk2bo0b6/gIih7Revgs20ROTTvLpc7qXZ9hXSt1 kZLz0SkUWEAmE8V/lKtDbRs= X-Google-Smtp-Source: AOwi7QAtZTgofhCxNdLZjXYDMXEEbjbVEdfE3J+BmB0KRoiwzlBvsCKIvFmkZaShNqcOdu2rfpjwbw== X-Received: by 10.28.132.69 with SMTP id g66mr12682677wmd.13.1506967773961; Mon, 02 Oct 2017 11:09:33 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id n43sm209658wrb.37.2017.10.02.11.09.32 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Oct 2017 11:09:33 -0700 (PDT) Date: Mon, 2 Oct 2017 19:09:31 +0100 From: Matt Smith To: Marco Beishuizen Cc: Don Lewis , mueller6722@twc.com, fullermd@over-yonder.net, freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002180931.GC48518@gmail.com> Mail-Followup-To: Matt Smith , Marco Beishuizen , Don Lewis , mueller6722@twc.com, fullermd@over-yonder.net, freebsd-ports@freebsd.org References: <201710021712.v92HCmdW033734@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 18:09:36 -0000 On Oct 02 20:01, Marco Beishuizen wrote: >On Mon, 2 Oct 2017, the wise Don Lewis wrote: > >>Yes it can. If you use the svn method when creating a jail you can >>chose any arbitrary source branch from the svn repository and then >>you can specify any desired svn revision on that branch when you >>update the jail. You would probably want to use this method when >>building ports for 12.0-CURRENT rather than creating the jail using >>a 12.0-CURRENT snapshot. > >I'm running 11.1-STABLE now, upgrading every few months or when there >is an important security fix. Do I have to build a new system twice in >that case (once my running system and once the poudriere jail)? > What I do is to initially create the jail using poudriere jail -c -j 11 -m src=/usr/src and then I upgrade the jail using poudriere jail -u -j 11. These commands use the existing /usr/src and /usr/obj trees from the host system buildworld/kernel. It doesn't need to be rebuilt. -- Matt From owner-freebsd-ports@freebsd.org Mon Oct 2 18:51:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2AE7E24A3B for ; Mon, 2 Oct 2017 18:51:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C20AB73630 for ; Mon, 2 Oct 2017 18:51:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v92IpXbH034114; Mon, 2 Oct 2017 11:51:37 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201710021851.v92IpXbH034114@gw.catspoiler.org> Date: Mon, 2 Oct 2017 11:51:33 -0700 (PDT) From: Don Lewis Subject: Re: Status of portupgrade and portmaster? To: mbeis@xs4all.nl cc: mueller6722@twc.com, freebsd-ports@freebsd.org, fullermd@over-yonder.net In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 18:51:44 -0000 On 2 Oct, Marco Beishuizen wrote: > On Mon, 2 Oct 2017, the wise Don Lewis wrote: > >> Yes it can. If you use the svn method when creating a jail you can >> chose any arbitrary source branch from the svn repository and then you >> can specify any desired svn revision on that branch when you update the >> jail. You would probably want to use this method when building ports >> for 12.0-CURRENT rather than creating the jail using a 12.0-CURRENT >> snapshot. > > I'm running 11.1-STABLE now, upgrading every few months or when there is > an important security fix. Do I have to build a new system twice in that > case (once my running system and once the poudriere jail)? Yes, but at least the poudriere jail doesn't build the kernel bits. The real pain point is that when you update the jail, the next bulk package build will toss all the previously built packages and force a full rebuild from scratch. That makes sense if you believe that the contents of the jail affect the contents of the packages build using that jail. If you don't think that is true, then why bother to update the jail. I stick to pretty much the same schedule as you for updating my -STABLE machines, though I'm doing it for 10.4-STABLE i386, 11.1-STABLE amd64 and i386, and 12.0-CURRENT amd64. I try to do weekly package update runs. From owner-freebsd-ports@freebsd.org Mon Oct 2 18:58:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B417E24C54 for ; Mon, 2 Oct 2017 18:58:23 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from lb3-smtp-cloud8.xs4all.net (lb3-smtp-cloud8.xs4all.net [194.109.24.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.xs4all.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 97ACB738B1; Mon, 2 Oct 2017 18:58:22 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan ([83.160.85.125]) by smtp-cloud8.xs4all.net with ESMTP id z5v1drPgwg5cRz5v2dzpyg; Mon, 02 Oct 2017 20:58:20 +0200 Received: from yokozuna (yokozuna [IPv6:0:0:0:0:0:0:0:1]) by yokozuna.lan (8.15.2/8.15.2) with ESMTPS id v92IwHgG073851 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Oct 2017 20:58:18 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Date: Mon, 2 Oct 2017 20:58:17 +0200 (CEST) From: Marco Beishuizen Sender: marco@yokozuna.lan Reply-To: Marco Beishuizen To: Matt Smith cc: Don Lewis , mueller6722@twc.com, fullermd@over-yonder.net, freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? In-Reply-To: <20171002180931.GC48518@gmail.com> Message-ID: References: <201710021712.v92HCmdW033734@gw.catspoiler.org> <20171002180931.GC48518@gmail.com> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-CMAE-Envelope: MS4wfOpDW4EsYVnHEQqVzJy7GN8CTL2Hy2k9LksoyvAmc+kPi3HA0pxDA+5tGaCsWBPfh1Fhd33YkYP0dY/FnCn6bO1dYFheQ+aZr5Qr9YU6IH1bww96T6D0 pSDGY/NAI2MrU+31lzRXhEpZvkiIMCUyIHpVg3VBXmp+IQFboEhhhNIJEEpim+HN3WgUv7ad/aLFt7ElWuBL5gfjm6ZBEJTxesZeFgEB2BvzfVy3TwQ6kz/L Y7eyVwvulTxBHRYLQapYvAJmGQReZaBMBegfJnfOTtFocdahw8VBVakkmLlW3+lc X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 18:58:23 -0000 On Mon, 2 Oct 2017, the wise Matt Smith wrote: >> I'm running 11.1-STABLE now, upgrading every few months or when there >> is an important security fix. Do I have to build a new system twice in >> that case (once my running system and once the poudriere jail)? >> > > What I do is to initially create the jail using poudriere jail -c -j 11 > -m src=/usr/src and then I upgrade the jail using poudriere jail -u -j > 11. > > These commands use the existing /usr/src and /usr/obj trees from the > host system buildworld/kernel. It doesn't need to be rebuilt. Did a make cleanworld last time I upgraded so /usr/obj is empty now, but next time I'll try this out. Didn't know poudriere could do this (although it's in the manpage I see now). Thanks for the info! Regards, Marco -- This sentence no verb. From owner-freebsd-ports@freebsd.org Mon Oct 2 19:02:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B751E24EA5; Mon, 2 Oct 2017 19:02:14 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C523573C2A; Mon, 2 Oct 2017 19:02:13 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id 196so1794050wmp.4; Mon, 02 Oct 2017 12:02:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:to:cc:reply-to:from:subject:message-id:date:user-agent :mime-version; bh=+nGuZa5reM9gXLA8ehxqgXJZvIhBs+D5zsVSSJZygKY=; b=YTQJMTzL8UmkHrIiby7juJbf1b83EypRSAbNuWUbrAQALqpxvxmtr2bRQuYDK0hP0t FjcHtCvZrCe+5sBdH3Y9/kOz+HO74UtatqJaOiYX7BWmTLV4Eotrydsqvt+twoHoZnvM 8TqojqCMcXTmaq+4SofvLsXz4ShBMOmYqAHSMvsXdxHi7gB2TNJIE05wLi3OHB2rB90i PyswZB7NWtI8LyTB6eBomWONt42F070KvszUlReCNBX6G7VInYF8bHffuZ5c1ozzjqWk YLSnnc0WM6J5K/JlKuFOB6snmuzovR1TAKnBrTO4Aar9BaKRpW6Lvtu3WE4iWZTBLmLI EjBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:cc:reply-to:from:subject:message-id :date:user-agent:mime-version; bh=+nGuZa5reM9gXLA8ehxqgXJZvIhBs+D5zsVSSJZygKY=; b=RL27baU3f2ZMWkGMRlcN47V3yu0B80ULhNdzsP15vjPbNBWGRjqnw/Hem3IfCDf9cb L/WPMVG4OyySLklaj5ZCH/8IKsVSBon/pN/PQaZG1HA6ihIL/l5qBXBGAmAAQzxskaVm mA2q8wXvH9VlNiR3oTVV1lVoznYr+n1/6V6Yeh1lXi0RQBETIaSV1c/xpGgjFuFVahG8 iVnrRnpV0kCo+ar3BW9HYzXnF3/RBHKDCPltIRLTDtSdcJ1VCpV2jwM04GFZEjZy7jYI o/+3cz4rt/l7c/FDy4RKxuO3Bp9iSnlytuF0Mk/zn5XBhTq6X/onytLAftGQxgPT7b5L V4yw== X-Gm-Message-State: AHPjjUhq43KBHvwV8obxjmw0t8ziNKT20ii7LpkIYYjxxS+JAgD5B8Nt rprUm+tBoUUzb/JTTBpBMBAyLqLA X-Google-Smtp-Source: AOwi7QAC7fBUrP5G5KTMQAnyyJh89y/S9lJ/Ipv5FFoCPky0CsUevpd8Up/nrJYzyfaobexSS7jv/w== X-Received: by 10.80.153.84 with SMTP id l20mr21270765edb.41.1506970931872; Mon, 02 Oct 2017 12:02:11 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:3265:ecff:fe8f:d3ec? ([2001:980:d7ed:1:3265:ecff:fe8f:d3ec]) by smtp.googlemail.com with ESMTPSA id b30sm10130270ede.1.2017.10.02.12.02.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Oct 2017 12:02:10 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= To: freebsd ports Cc: freebsd-ports-announce@freebsd.org Reply-To: freebsd ports From: =?UTF-8?Q?Ren=c3=a9_Ladan?= Subject: New 2017Q4 branch Message-ID: <7ad0b7be-c611-4cd8-50c3-a3a4d74d7d46@freebsd.org> Date: Mon, 2 Oct 2017 21:01:57 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="po67IGiD7SuoABas3M9rJQSxViSBCc2Co" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 19:02:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --po67IGiD7SuoABas3M9rJQSxViSBCc2Co Content-Type: multipart/mixed; boundary="6vjagmqpGwEBlCG7iP02U5GX3G2AKauKs"; protected-headers="v1" From: =?UTF-8?Q?Ren=c3=a9_Ladan?= Reply-To: freebsd ports To: freebsd ports Cc: freebsd-ports-announce@freebsd.org Message-ID: <7ad0b7be-c611-4cd8-50c3-a3a4d74d7d46@freebsd.org> Subject: New 2017Q4 branch --6vjagmqpGwEBlCG7iP02U5GX3G2AKauKs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi, The 2017Q4 branch has been created. It means that the next update on the quarterly packages will be on the 2017Q4 branch. A lot of things happened in the last three months: - pkg 1.10.1 - New USES: (none) - Removed USES: execinfo twisted - New keywords: (none) - Removed keywords: (none) - Default version of GCC switched to 6 - Firefox 56.0 - Firefox-esr 52.4.0 - Chromium 61.0.3163.100 - Ruby 2.2.8, 2.3.5, 2.4.1 - gcc 6.4.0 - ghc 8.0.2 - devel/cmake-modules merged into devel/cmake - devel/cargo merged into lang/rust, as Cargo is now provided with Rust Next quarterly package builds will start on Tuesday October 3th, at 1:00 PM and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 5876 Number of committers: 175 Most active committers: 1542 sunpoet 261 amdmi3 215 jbeich 180 swills 153 olgeni 148 dbaio 144 ultima 126 antoine 120 jrm 104 mat Diffstat: 16612 files changed, 245701 insertions(+), 152531 deletions(-) and on the 2017Q3 branch: Number of commits: 345 Number of committers: 54 Most active committers: 59 feld 51 jbeich 40 tz 18 sunpoet 17 cpm 13 koobs 11 riggs 8 ultima 8 junovitch 8 joneum Diffstat: 955 files changed, 13462 insertions(+), 16764 deletions(-) Regards, Ren=C3=A9 Ladan --6vjagmqpGwEBlCG7iP02U5GX3G2AKauKs-- --po67IGiD7SuoABas3M9rJQSxViSBCc2Co Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+zdFyG8V6O2sgTL82ClOw7vE19UFAlnSjTEACgkQ2ClOw7vE 19X3PQgAj/XHrSdGOW0N1ZTtY4m3VVRmU2+dfMgVmuGk1RyVVW8Qh+fMj39A1bME /HsthM1rLQ3eKpQ3Wo8DosGX+ze8VN8aWeGcB2zG5H966xTFhDsShD18Zy4qAKz2 3QV0kYRoYS/egE75SixXAr3b9UcGKlaeOAHHWBGdOkZeKwvBsH4BiQ3UAId95DCB VxtifNvvSvxFWRDvgNf48b3TbYCnC+jS5LPI6uM1YdPDQpGWT1hf7Dz+ZqCB6bHJ +MzmmyJfScpY3S5epyKtVGd5XLT9STW0qgJHWJahMjjO7xkvOu9vwbGOo2YwcWYP TE0UVYyYDu/TksRmsde/AhDgFOG3+Q== =T0yV -----END PGP SIGNATURE----- --po67IGiD7SuoABas3M9rJQSxViSBCc2Co-- From owner-freebsd-ports@freebsd.org Mon Oct 2 19:55:02 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FD4AE262F2 for ; Mon, 2 Oct 2017 19:55:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 21D5475890; Mon, 2 Oct 2017 19:55:01 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v92Jt15J022157; Mon, 2 Oct 2017 19:55:01 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v92Jt1ll022156; Mon, 2 Oct 2017 12:55:01 -0700 (PDT) (envelope-from david) Date: Mon, 2 Oct 2017 12:55:01 -0700 From: David Wolfskill To: Don Lewis Cc: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002195501.GH1222@albert.catwhisker.org> Reply-To: freebsd-ports@freebsd.org References: <201710021851.v92IpXbH034114@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3gNIKMlg37D5iFb5" Content-Disposition: inline In-Reply-To: <201710021851.v92IpXbH034114@gw.catspoiler.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 19:55:02 -0000 --3gNIKMlg37D5iFb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 02, 2017 at 11:51:33AM -0700, Don Lewis wrote: > On 2 Oct, Marco Beishuizen wrote: > ... > > I'm running 11.1-STABLE now, upgrading every few months or when there i= s=20 > > an important security fix. Do I have to build a new system twice in tha= t=20 > > case (once my running system and once the poudriere jail)? >=20 > Yes, but at least the poudriere jail doesn't build the kernel bits. The > real pain point is that when you update the jail, the next bulk package > build will toss all the previously built packages and force a full > rebuild from scratch. That makes sense if you believe that the contents > of the jail affect the contents of the packages build using that jail. > If you don't think that is true, then why bother to update the jail. >=20 > I stick to pretty much the same schedule as you for updating my -STABLE > machines, though I'm doing it for 10.4-STABLE i386, 11.1-STABLE amd64 > and i386, and 12.0-CURRENT amd64. I try to do weekly package update > runs. > .... With respect, that (building the world twice -- once for the host and once for the poudriere jail) has not been my experience. As described in and (particularly the "Postscript: Subsequent Maintenance" section at the bottom of the latter page), the machine that runs poudriere gets its stable/11 environment updated daily; it runs poudriere twice each week (Saturday and Sunday), and the thus-refreshed local repository is used weekly (on Sunday). As a case in point, on Saturday last (2 days ago, as of this writing), the host system was updated from: FreeBSD 11.1-STABLE #469 r324085M/324100:1101505: Fri Sep 29 03:39:21 PDT = 2017 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC = amd64 to=20 FreeBSD 11.1-STABLE #470 r324115M/324116:1101505: Sat Sep 30 03:41:57 PDT = 2017 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC = amd64 the ports working copy was updated from r450887 to r450972, and the ensuing poudriere run recorded: [11amd64-ports-home] [2017-09-30_10h55m37s] [committing:] Queued: 1091 Buil= t: 1091 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 0 Time: 04:28= :37 The following day, the host system was updated from: FreeBSD 11.1-STABLE #470 r324115M/324116:1101505: Sat Sep 30 03:41:57 PDT = 2017 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC = amd64 to FreeBSD 11.1-STABLE #471 r324138M/324155:1101505: Sun Oct 1 03:42:38 PDT = 2017 root@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC = amd64 the ports working copy was updated from r450972 to r451042, and the ensuing poudriere run recorded: [11amd64-ports-home] [2017-10-01_10h50m40s] [committing:] Queued: 183 Built= : 183 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 0 Time: 01:42:10 Disclaimer: I do not claim expertise in ports-system wrangling. While I use poudriere to build packages for my systems that are only updated weekly, I use portmaster for those that are updated daily. I make no claims of optimal ... anything, really. What I describe seems to generally work for me, but my approaches are almost certainly not suitable for most folks. Despite that, it may be possible to learn things from what others have done, so I have tried to document what I did; please feel free to use it -- possibly as an example of what NOT to do. :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org http://www.cbc.ca/news/opinion/donald-trump-playbook-1.4265374 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --3gNIKMlg37D5iFb5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZ0pmVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X7iIH/2w0aKwQqNQl0BHebPqVFuxW X7E2cOleUViSsmoh7M68eFfV2Xpf9RU0uwPIioBPcseZa/NaMX7QaCB4larO8T8B m1TA7U6lL0qlMQBlwWhnEntASB7ghPbx7m214c5PUwY4Iiaji4rECeL3JebarmA3 JeWTwYyUiOErP29huU2zpkE1yxZok4WhOHeEreqgTGmOA5B97Jg3sCa/nevDJbuZ sdlwSJ1lgdPktS9QF8NT2144EXt7vlSMuSIHMl02ZNIl6e3PVBvtjsRjRE4cpWBw 3E+U1s7w6DNs7o3+6CoSmBIu9N1CSWxLDJgI2aXYNik609EPKoMozuj+aPwhkGQ= =+U8a -----END PGP SIGNATURE----- --3gNIKMlg37D5iFb5-- From owner-freebsd-ports@freebsd.org Mon Oct 2 20:04:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51CA6E268B1 for ; Mon, 2 Oct 2017 20:04:32 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D668E76095; Mon, 2 Oct 2017 20:04:31 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id p46so2391902wrb.0; Mon, 02 Oct 2017 13:04:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=xa30aROKIgLSA441iOpvKxHHWq6Jf5u4JgB9iR9ktt8=; b=Xndpc1nsFpRsqskn7PmSibFRrp++qNz6N4hKVr8Rw5wOB3j7nMq6CWXRqZxTMzOjr5 30lubiejnS0KXLwoFupGy/GyVLojatOn8+OPReeY+GaPbbIKJYL4765Q2R3EMmryt/+t hPbjEa2I5VzoAz4iWgFp6Xi+QshVCD+czplkEP2mg5vgKptn+6vwF2zgnFOC6+gJTdxV 9pRVRSqhdqd307sAwBjymun3vWMt/z9J5koHhBpaRceNvkVpdb9AL+FKJ+IMd2tS0Cvu J4u86Mh+PBI9ja02Hj/GupXwlM6KBNQqr9YLn/cJAoN19PeQbwqvrasl5ussZAfPdrcL 75Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=xa30aROKIgLSA441iOpvKxHHWq6Jf5u4JgB9iR9ktt8=; b=nGxU1WkVkug6YxDXT4v07S6qyy5vgMnjalLGf0vlHkzeOjgCwL6kZmCc7+262BspeY PIxrzAvYjG15U1W0uSn8nb6RgFfwbn/RrKYy2HCQkykh6oFAuZGF1hQNX2bs0GyZoyFV LxYNj3GMGTC0ZR8Yq6HeXX5L7anJomf97kCtc0beewmKENcHny6oP/AWrJSlXLWnMiya rbeq8BSQdUxn7p8b4UMeR5BcNXK0XL/ydQS1AYn22ZO2MG3W5ri7CR5+FAWpImfzIick wv7Cbs8RHM2jbgWn4JSUSwHhXmD+0Z44yT2aJvX5gPqIQXmJH8XAZImTkG2a2RvDOS7g 8uMw== X-Gm-Message-State: AMCzsaXb3Sv5lu0hDUf0Ifgb/gOLMdJXYx3ermkCIqiRVZvn+2krofiy YkVE6YcY5JyufWpOqPTPjcyAP7Wr5jY= X-Google-Smtp-Source: AOwi7QAZfgqMEq/3VcrzcIGYcvQ5Bk34LbUZ6JqIkCtSCV6vzCBoa3JnzYE7ot/tHVxMIoiCuqu4xw== X-Received: by 10.223.151.10 with SMTP id r10mr8360389wrb.162.1506974670285; Mon, 02 Oct 2017 13:04:30 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id w2sm15692086wrb.67.2017.10.02.13.04.29 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Oct 2017 13:04:29 -0700 (PDT) Date: Mon, 2 Oct 2017 21:04:28 +0100 From: Matt Smith To: Don Lewis Cc: mbeis@xs4all.nl, mueller6722@twc.com, fullermd@over-yonder.net, freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Message-ID: <20171002200427.GD48518@gmail.com> Mail-Followup-To: Matt Smith , Don Lewis , mbeis@xs4all.nl, mueller6722@twc.com, fullermd@over-yonder.net, freebsd-ports@freebsd.org References: <201710021851.v92IpXbH034114@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <201710021851.v92IpXbH034114@gw.catspoiler.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 20:04:32 -0000 On Oct 02 11:51, Don Lewis wrote: > >Yes, but at least the poudriere jail doesn't build the kernel bits. The >real pain point is that when you update the jail, the next bulk package >build will toss all the previously built packages and force a full >rebuild from scratch. That makes sense if you believe that the contents >of the jail affect the contents of the packages build using that jail. >If you don't think that is true, then why bother to update the jail. That is a good point and it does seem an overkill if you think not much has changed in the jail to warrant it. It doesn't do it every time, only when they increment the osrel number. There is a way around it. I sometimes run this script which updates the jail to be the same as my host. #/bin/sh V1=`uname -r` V2=`sysctl -n kern.osreldate` JV=`find /var/poudriere/data/packages/ -depth 2 -name .jailversion` echo "${V1} ${V2}" > ${JV} echo "${JV} set to ${V1} ${V2}" -- Matt From owner-freebsd-ports@freebsd.org Mon Oct 2 21:32:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD24AE282F0 for ; Mon, 2 Oct 2017 21:32:17 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward101p.mail.yandex.net (forward101p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 826E07C7E9 for ; Mon, 2 Oct 2017 21:32:17 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from mxback1j.mail.yandex.net (mxback1j.mail.yandex.net [IPv6:2a02:6b8:0:1619::10a]) by forward101p.mail.yandex.net (Yandex) with ESMTP id 237AE6A832C7; Tue, 3 Oct 2017 00:32:14 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback1j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ygpWXbVyAE-W7V4iu9X; Tue, 03 Oct 2017 00:32:08 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1506979928; bh=qajLp4ghcDU6iENVHAmwQPz6ENIg+g1N3oEEaG0yLBU=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References; b=ZXPonDfAq2/GeXS+ZYNbY4QlzNcAJBi06vPAeqIzDfwgD7I183cnnr6sByYpk/9Yx K0PcdErhAYNk4pLOq6tWQdwdlSMCPAHb4vp6EvTx8qbZtQf25RW4dXIZt4/M2LPIVG V0pRIhrSy7ioG2rwiFvQj3nbR78I+ekU2d/9GkfU= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id mLPKBgf6yS-W5s4BAog; Tue, 03 Oct 2017 00:32:06 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1506979926; bh=qajLp4ghcDU6iENVHAmwQPz6ENIg+g1N3oEEaG0yLBU=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References; b=NWqlyieCUUkCBYC5tGKRL30mL6THZv8rZVH50sI38oT7OGA9ZblUMe9mkaP3w0TXu QmllSxSzhD275ClT5Ghexry6/f4u3OnC0OqKV6+X/EZfQ5ce5fIOC6Nz0A82DnrvaZ LMXfsUZ+4DLs7aY2Wy12R544At6/aSKA6fWHk51s= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1506979923.25718.2.camel@yandex.com> Subject: Re: Status of portupgrade and portmaster? From: Stari Karp To: abi , FreeBSD , Carmel NY Date: Mon, 02 Oct 2017 17:32:03 -0400 In-Reply-To: <77f800a1-0806-acb1-2854-33cba3793c39@abinet.ru> References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <20170929182305.GE86601@home.opsec.eu> <20170929183448.GA175@gmail.com> <77334fc4-b64e-45ed-a443-4076e47acee3@BY2NAM03FT029.eop-NAM03.prod.protection.outlook.com> <01cc2d44-ba19-1618-a31a-760218545e12@FreeBSD.org> <77f800a1-0806-acb1-2854-33cba3793c39@abinet.ru> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 21:32:18 -0000 On Mon, 2017-10-02 at 12:26 +0300, abi wrote: > 02.10.2017 12:07, Carmel NY пишет: > > While it will undoubtedly work, it is still more complex than the > > average > > desktop user requirers. > > Building from ports is already more complex thing than one could > expect > from desktop user. I don't think ports are recommended way to keep > system updated. It you use ports, you change port options (why would > you > use them if not), so you are on narrower path - non-default options > are > not QA tested, can conflict with each other and within dependency > chain, etc > > Synth fits the bill nicely by being, for the most > > part, easy to understand and run. I am already on my forth "ports > > maintenance" > > program having used portmanager, portmaster, portupgrade and now > > synth. At > > this point, I would almost rather switch to a new OS before > > abandoning synth > > for something that IMHO is just overkill for the average user. > > You know, this is open source, right? You may pick up ADA stack, > I'm > sure J Marino will give you some ideas how to overcome ino64 issue. > Here is Marino's post on the FreeBSD forum about ino64 issue: https://forums.freebsd.org/threads/62633/ From owner-freebsd-ports@freebsd.org Tue Oct 3 00:28:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 362FDE2B455 for ; Tue, 3 Oct 2017 00:28:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-28.reflexion.net [208.70.210.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0167811B6 for ; Tue, 3 Oct 2017 00:28:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 1888 invoked from network); 3 Oct 2017 00:22:17 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 3 Oct 2017 00:22:17 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Mon, 02 Oct 2017 20:22:17 -0400 (EDT) Received: (qmail 1973 invoked from network); 3 Oct 2017 00:22:11 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 3 Oct 2017 00:22:11 -0000 Received: from [192.168.1.26] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 84284EC9390; Mon, 2 Oct 2017 17:22:10 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: devel/llvm40 and llvm50 builds vs. powerpc (32-bit) FreeBSD: "Host compiler appears to require libatomic, but cannot find it." Message-Id: <89A2CEC3-A1E0-4409-8354-37D827348C60@dsl-only.net> Date: Mon, 2 Oct 2017 17:22:09 -0700 To: brooks@FreeBSD.org, FreeBSD Toolchain , FreeBSD PowerPC ML , FreeBSD Ports X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 00:28:59 -0000 This is a system where world was built with system clang 5 and there is no gcc 4.2.1 installed: only the system-clang are on the old PowerMacs I'm testing on. The building of ports was via poudriere and system clang. Even with the lldb build, the lld build, the LIT build, the Extras build, and the Docs build disabled the below happens for 32-bit powerpc --on both devel/llvm40 and devel/llvm50 . Note that the system-clang-5 builds fine, despite lack of 64-bit atomics, including building WITH_CLANG_FULL=3D and WITH_CLANG_EXTRAS=3D . Building devel/llvm40 and devel/llvm50 works fine targeting powerpc64 instead of 32-bit powerpc. As for 32-bit powerpc goes. . . I would expect lldb to need to be disabled. Possibly lld as well. (Also, neither would work if they built as I understand.) Extras might be a mix of things that could be built and things that can not for 32-bit powerpc --but might all be buildable? Doc should probably be fine to build. The problem ( devel/llvm40 example): . . . ---Begin OPTIONS List--- =3D=3D=3D> The following configuration options are available for = llvm40-4.0.1_1: CLANG=3Don: Build clang DOCS=3Doff: Build and/or install documentation EXTRAS=3Doff: Extra clang tools LIT=3Doff: Install lit and FileCheck test tools LLD=3Doff: Install lld, the LLVM linker LLDB=3Doff: Install lldb, the LLVM debugger =3D=3D=3D> Use 'make config' to modify these settings ---End OPTIONS List--- . . . -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Failed -- Looking for __atomic_load_8 in atomic -- Looking for __atomic_load_8 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:74 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:307 (include) CMakeLists.txt:582 (include) -- Configuring incomplete, errors occurred! See also = "/wrkdirs/usr/ports/devel/llvm40/work/.build/CMakeFiles/CMakeOutput.log". See also = "/wrkdirs/usr/ports/devel/llvm40/work/.build/CMakeFiles/CMakeError.log". *** Error code 1 Stop. make: stopped in /usr/ports/devel/llvm40 =3D>> Cleaning up wrkdir =3D=3D=3D> Cleaning for llvm40-4.0.1_1 build of devel/llvm40 | llvm40-4.0.1_1 ended at Mon Oct 2 17:16:35 PDT = 2017 build time: 00:05:14 !!! build failure encountered !!! Context details: # uname -apKU FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r324071M powerpc = powerpc 1200047 1200047 # cc --version FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on = LLVM 5.0.0svn) Target: powerpc-unknown-freebsd12.0 Thread model: posix InstalledDir: /usr/bin # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: https://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 450478 Last Changed Rev: 450478 # more ~/src.configs/src.conf.powerpc-clang-bootstrap.amd64-host=20 TO_TYPE=3Dpowerpc # KERNCONF=3DGENERICvtsc-NODBG TARGET=3D${TO_TYPE} .if ${.MAKE.LEVEL} =3D=3D 0 TARGET_ARCH=3D${TO_TYPE} .export TARGET_ARCH .endif # WITH_CROSS_COMPILER=3D WITHOUT_SYSTEM_COMPILER=3D # WITH_LIBCPLUSPLUS=3D WITH_BINUTILS_BOOTSTRAP=3D WITH_ELFTOOLCHAIN_BOOTSTRAP=3D WITH_CLANG_BOOTSTRAP=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D WITH_CLANG_FULL=3D WITH_CLANG_EXTRAS=3D WITHOUT_LLD=3D # lldb requires missing atomic 8-byte operations for powerpc (non-64) WITHOUT_LLDB=3D # WITH_BOOT=3D WITHOUT_LIB32=3D # WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GCC_IS_CC=3D WITHOUT_GNUCXX=3D # NO_WERROR=3D # # Use WERROR to avoid stopping at the likes of: # error: implicit conversion from 'int' to 'int8_t' (aka 'signed char') = changes value from 128 to -128 [-Werror,-Wconstant-conversion] WERROR=3D MALLOC_PRODUCTION=3D # WITH_REPRODUCIBLE_BUILD=3D WITH_DEBUG_FILES=3D =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Tue Oct 3 04:20:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D460E2FC51; Tue, 3 Oct 2017 04:20:48 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB4E23F61; Tue, 3 Oct 2017 04:20:47 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-102-127.dyn.iinet.net.au [106.68.102.127]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v934KgZF036286 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Oct 2017 21:20:45 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [maybe spam] New 2017Q4 branch To: freebsd ports , =?UTF-8?Q?Ren=c3=a9_Ladan?= Cc: freebsd-ports-announce@freebsd.org References: <7ad0b7be-c611-4cd8-50c3-a3a4d74d7d46@freebsd.org> From: Julian Elischer Message-ID: <6ea6bcb5-d27f-0ccb-8a79-b616403c24d0@freebsd.org> Date: Tue, 3 Oct 2017 12:20:36 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <7ad0b7be-c611-4cd8-50c3-a3a4d74d7d46@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 04:20:48 -0000 On 3/10/17 3:01 am, René Ladan wrote: can we please have a way of finding out the revision at which the latest HEAD branch compile was done at? (and for that matter the latest recompile on the quarterly branch). > Hi, > > The 2017Q4 branch has been created. It means that the next update on the > quarterly packages will be on the 2017Q4 branch. > > A lot of things happened in the last three months: > - pkg 1.10.1 > - New USES: (none) > - Removed USES: execinfo twisted > - New keywords: (none) > - Removed keywords: (none) > - Default version of GCC switched to 6 > - Firefox 56.0 > - Firefox-esr 52.4.0 > - Chromium 61.0.3163.100 > - Ruby 2.2.8, 2.3.5, 2.4.1 > - gcc 6.4.0 > - ghc 8.0.2 > - devel/cmake-modules merged into devel/cmake > - devel/cargo merged into lang/rust, as Cargo is now provided with Rust > > Next quarterly package builds will start on Tuesday October 3th, at 1:00 > PM and > should be available on your closest mirrors few days later. > > For those stat nerds out there, here's what happened during the last 3 > months on head: > Number of commits: 5876 > Number of committers: 175 > Most active committers: > 1542 sunpoet > 261 amdmi3 > 215 jbeich > 180 swills > 153 olgeni > 148 dbaio > 144 ultima > 126 antoine > 120 jrm > 104 mat > Diffstat: 16612 files changed, 245701 insertions(+), 152531 deletions(-) > > and on the 2017Q3 branch: > Number of commits: 345 > Number of committers: 54 > Most active committers: > 59 feld > 51 jbeich > 40 tz > 18 sunpoet > 17 cpm > 13 koobs > 11 riggs > 8 ultima > 8 junovitch > 8 joneum > Diffstat: 955 files changed, 13462 insertions(+), 16764 deletions(-) > > Regards, > René Ladan > From owner-freebsd-ports@freebsd.org Tue Oct 3 06:35:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0162E325EB for ; Tue, 3 Oct 2017 06:35:42 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1C066AE7 for ; Tue, 3 Oct 2017 06:35:42 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:fd52:b25f:64ce:923f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id BC8E132CA for ; Tue, 3 Oct 2017 06:35:38 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: Status of portupgrade and portmaster? To: freebsd-ports@freebsd.org References: <201710021712.v92HCmdW033734@gw.catspoiler.org> <20171002180931.GC48518@gmail.com> From: Matthew Seaman Message-ID: <59cf6911-ab70-d222-d4a3-e7106c242efb@FreeBSD.org> Date: Tue, 3 Oct 2017 07:35:32 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="J4XSBgM0O7R6AOebagqHCsAvP2dwRciwB" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 06:35:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --J4XSBgM0O7R6AOebagqHCsAvP2dwRciwB Content-Type: multipart/mixed; boundary="3t8LgdsN2mqRUXeCQL4S3987vKxqXiQn6"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <59cf6911-ab70-d222-d4a3-e7106c242efb@FreeBSD.org> Subject: Re: Status of portupgrade and portmaster? References: <201710021712.v92HCmdW033734@gw.catspoiler.org> <20171002180931.GC48518@gmail.com> In-Reply-To: --3t8LgdsN2mqRUXeCQL4S3987vKxqXiQn6 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 02/10/2017 19:58, Marco Beishuizen wrote: > On Mon, 2 Oct 2017, the wise Matt Smith wrote: >=20 >>> I'm running 11.1-STABLE now, upgrading every few months or when there= >>> is an important security fix. Do I have to build a new system twice >>> in that case (once my running system and once the poudriere jail)? >>> >> >> What I do is to initially create the jail using poudriere jail -c -j >> 11 -m src=3D/usr/src and then I upgrade the jail using poudriere jail = -u >> -j 11. >> >> These commands use the existing /usr/src and /usr/obj trees from the >> host system buildworld/kernel. It doesn't need to be rebuilt. >=20 > Did a make cleanworld last time I upgraded so /usr/obj is empty now, bu= t > next time I'll try this out. Didn't know poudriere could do this > (although it's in the manpage I see now). Thanks for the info! Even so, so long as your host system and your poudriere jail are ABI compatible, then you *don't* need to upgrade your pourdiere jail in lock-step with your host. The poudriere jail only needs to be binary compatible -- ie. the same major version of FreeBSD -- and not newer than the host system. Even the reason for having the same major version is just so that the packages you build will run where you want to deploy them -- you can run a jail of an earlier major version if you have older systems to support, or you can run an i386 jail on an amd64 server if you have 32bit machines to support. Not upgrading your poudriere jail has one big advantage -- as soon as you update the jail, poudriere will rebuild /all/ of your packages. Avoiding updating the jail means you can just carry on doing incremental updates and save some CPU cycles. Cheers, Matthew --3t8LgdsN2mqRUXeCQL4S3987vKxqXiQn6-- --J4XSBgM0O7R6AOebagqHCsAvP2dwRciwB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ0y+6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATHQ4P/3IvLoEGIrpcCt93DfaNTYuH nShqW2rbwUAODIhNSh5H3ao24QOh2wxbPYkgz8s/cZxwqif7FK6g1hqREWbjDcn6 rK/5HM8Pn8z476MUdmOa440o6yHylljqgpAB0sSUWQ3lkTnSYAvE0jsNAP2KK+6U NbspoUa0fHMHzMPDDpJJIKp0BlF7tyYR3Hd15iGZVzslXF/0bu5VaWLaHe5BjAeL CTRwhnyJHpwK/AxQxZswqH4xy+zQ99CzCgy4bGT/cAlVgWcT/PzjdxylGq1bViLm vM+3uDAAuZTvPAEYeXPoe6N5fHvvD/M7osKCOBj4h9xAjNiDLk/sYj4w5AT7UmE3 ZSdhIbn8yLY/3vzWZ3A+GqNcmdB5Xj+anP6LPHapuqixzfNEQgx9h5ysdZeTrg3o 92jm6psmBTT4d+j/LONaOMfoIAgtwVypRIWAgxCpbFeX2Xe9srPi2p/6nVnSlR1P xuiapZvGOpo9jPnHCPlFyAXHp+SZsAZ2J4tOO4wbg3jcxUf7gOv4uuSvpbjyEMVf KiDmNvYv9QZLSm5/cvkK8BSHzfJUv8hDJh5kTST2Lg4zoVbHzkUY2HvNoyNcWXu8 5ijoWAXuYSTZZ2e1++SuBcQHAfeGXwgr4sWbDPkD0+0xUhlHwu23COyK5QMKcyuL ho9cFoaY/TXiI+QwJMo8 =VmCz -----END PGP SIGNATURE----- --J4XSBgM0O7R6AOebagqHCsAvP2dwRciwB-- From owner-freebsd-ports@freebsd.org Tue Oct 3 06:35:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F826E32601 for ; Tue, 3 Oct 2017 06:35:55 +0000 (UTC) (envelope-from acu.ilie.dorin@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1311266B53 for ; Tue, 3 Oct 2017 06:35:55 +0000 (UTC) (envelope-from acu.ilie.dorin@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id p187so12743641oif.4 for ; Mon, 02 Oct 2017 23:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=G3eo12rKI+dVIkfvUcvkWfb5/1XWGr63Ky8UTvDZQyQ=; b=TAWpveX7f1hC8oDe1zZORMxFKd0i3FCU6RnREGGw59qhMyRybooaTXWc424VtTE28N shnpjrdmameTeK8HgzLbv/yGsof1E3aEIzYpRvpds26+q6U3+GuFUGsPRjMdbJuvnPGv /8a/zCL7g/qbq0JbS6F/eEYXQFaz+GvDQksZy5Thyq3kRAq20kRrvmPKl+388PRaT9kd H0T+O6XSnKAYkpQtPmdB4xs8/K/XeLpo7ZKB82YSwiO610Zh9TsLBWYDl5OiNIfzAnTf jiL4Wp3jezbkNN9nrgSW9CGxlfoKRbxjShA1df9QAcRt8sOWP6E3md4LePHcbMkTjVcO VTgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=G3eo12rKI+dVIkfvUcvkWfb5/1XWGr63Ky8UTvDZQyQ=; b=Na/I/oIrq+LC6Hb0y6PSR40rzd/FSLeGCZzjTcHeXmEF4UqPt/vrnqSsnjVTIrZf5D EWUg2kOqZqepulI+Zhhc5x07J7Z3tSqT5pYOpfpBVqbx3z0FhEesXQHqaBk1ZieGBYg4 iGEsREfIDthSFP9vWNlUaAYkSIYqn3qXzvrgUkan2KudM1hSPHMYUYO/HU3BXUvLDWdu 7jfAymHNPhJ1QAfArx7VuJfpMWZO/npJ6jnZY/OGeflWlpbOP6XTQKVYw0wnoF1vB9Oh 4gmhpVskkfN3ljwhxZQKyX46Yr4e8XQ+ylj+QnP+/Jp4ynb3DPdIWIgfBPucgf+3v+R6 UlDg== X-Gm-Message-State: AMCzsaUCVVxG3e9ej6xCwNwjuzhANNSB7E+DEV+tmiRq356otogNBYv2 nXAgN/7X42S/8oQHsjcdXUxO8ExR0oEEi3Vf+Q62ag== X-Google-Smtp-Source: AOwi7QC2+fuEOomeu473W5tAsIKntUrCudzga7Ai0/MbFoe+RxBxOxailL4zX5Wz10zmg6fgNUJ3Xgh9mpqtPN9zkQE= X-Received: by 10.202.7.198 with SMTP id 189mr7849981oih.18.1507012554089; Mon, 02 Oct 2017 23:35:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.83.201 with HTTP; Mon, 2 Oct 2017 23:35:53 -0700 (PDT) From: Acu Ilie Dorin Date: Tue, 3 Oct 2017 01:35:53 -0500 Message-ID: Subject: NextCloud 12.03 is Released - when it will be added to freshports ? To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 06:35:55 -0000 Hello Everyone, I wonder what is the procedure to find out whether anyone is working on getting Nextcloud 12.03 in freshports.. It see that a lot of bugs were fixed... . https://github.com/nextcloud/server/pulls?page=1&q=is%3Apr+milestone%3A%22Nextcloud+12.0.3%22+is%3Aclosed And the repos for 12.03 are available https://download.nextcloud.com/server/prereleases/ https://nextcloud.com/install/#instructions-server Thank you. From owner-freebsd-ports@freebsd.org Tue Oct 3 08:01:48 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4B27E343B9 for ; Tue, 3 Oct 2017 08:01:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A3FC69879 for ; Tue, 3 Oct 2017 08:01:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dzI9C-0004Lc-9f; Tue, 03 Oct 2017 10:01:46 +0200 Date: Tue, 3 Oct 2017 10:01:46 +0200 From: Kurt Jaeger To: Acu Ilie Dorin Cc: freebsd-ports@freebsd.org Subject: Re: NextCloud 12.03 is Released - when it will be added to freshports ? Message-ID: <20171003080146.GM86601@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 08:01:48 -0000 Hi! > Hello Everyone, I wonder what is the procedure to find out whether anyone > is working on getting Nextcloud 12.03 in freshports.. Look at bugs.freebsd.org and search for nextcloud. You will find https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222738 and now we wait for maintainer approval. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Tue Oct 3 08:51:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E011CE356BB; Tue, 3 Oct 2017 08:51:41 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4600B6AF4B; Tue, 3 Oct 2017 08:51:40 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.55.72.205]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LwrPM-1dFDci1tsG-016Rq2; Tue, 03 Oct 2017 10:51:32 +0200 Date: Tue, 3 Oct 2017 10:51:24 +0200 From: "O. Hartmann" To: FreeBSD CURRENT , FreeBSD Ports Subject: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64? Message-ID: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/8_/KV1nqqQOtqpC05WlGfe."; protocol="application/pgp-signature" X-Provags-ID: V03:K0:RR8I8SMQhgwBE9OSDwHK9lXN8SHbo8I3u3rU+7yNbXQDiejtIGw 3aL5nkzjbtl83GveqhI+XG7/p2h+CSk66RWMdDqNTe2I8OrlTiIEUtH+sw+X6lMXf1UcnVE YgbIRJAT1HvMswBFKRzgRIdOhcGqw3XSUHNtlc6VEIrJsfYCLtMZlky8qiiixx4pXga4Byh AxISxoAKI1HlyPsgcqYUA== X-UI-Out-Filterresults: notjunk:1;V01:K0:vTYWvkg4ytc=:ij+GeipPoqU1EFhEElQpo7 8Ux6Jb9yluXQ2vLfqB79nadbNht8q6MrO39JeGTeJ0lN7F9HTq00m3jq8OThInAjgb7SmMQuC vDu+jJ0wsjzLjzJ23uRYxekC6R0/0Ur9jpYrFDhDvCCaRzF9fUa7lUXgEkP9+F2g6p19g+pzg gyP849EjhB+6wmT3G/v1stX43wHwc5Z0xlOO3foXPTAjNj2Y4dQms1b0B5Y/jlm5czz+BuRI8 35tBE1q5+T45ut/3mMuwfaSuy0YZ6k0bmZxAwlxdBRMwmfF3hp7dxZl7nv6kx6ufiUOhBS5kN 2a3j3QJfyNVpEeP1n0b+MFEGnNFYlrzHlwVOyee4L9IhlfZkNtK1CpM8FLEwgIaHBKIoDaoBF 5iMy9hSljwf1O40a7KZ4wR0k/9cu2j21FOc3dpbuNMZMqxcxv3Om1C+B7GvwgYuOpc8tP3d41 25qC98UFy3NNg9re4QhOEd3tPCSp3U+ydgN1+8EVbFeOvfLCOqwrXn5NhyF041ckpZKJlRVHr pOzTdxTdajdwbT2mnor39luoQxdyEBg4+fCMLQ+lVzPOxvL6hyI9EMdWiJCqfS6N8778MK4Gm dmpAmXbzMzE5fNqpnrUIP7QD66UPej74pD+HHIB4A00dkMdJLI7LyQ7lioi3npLeG8T5Dzf1j 58DFFrBhD7C75VZJrKdX66haYDU/ryJzsOajRo/LWa3sLe5majQ3pZDSdhrOv8XF3mlJY1eJ4 Wyz6UMuNgYwXgxuUfi5JCANDnMwEPw3mQPpnCAQx9i2/05d16cFh3rUkC+TlrTymF7Wfdky3s l9gbrab8tOSJL0h3/URXrRjt087IA== X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 08:51:42 -0000 --Sig_/8_/KV1nqqQOtqpC05WlGfe. Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable When using "poudriere", it seems ABI is freebsd:12:x86:64. When using FreeB= SD base, it seems always to be referred to FreeBSD:12:amd64. What now? All non-BSD worl= d uses x86:64, FreeBSD is using amd64, but why is this used inconsistently all over the pl= aces? I run into trouble setting up some package- and base-servers and ran into t= he problem when deleting - not thinking of this discovered inconsistency - some links = on the servers regarding FreeBSD:12:x86:64 (the same is for 11-STABLE). Can someone shed some light onto this?=20 What am I supposed to use now? The handbook referes to amd64, so I thought = poudriere would, too.=20 Thanks in advance, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/8_/KV1nqqQOtqpC05WlGfe. Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWdNPjAAKCRDS528fyFhY lFgbAgCQ2dz1RSaZ2eAEqBpyQV5Nde85edLswg45tkw2vc1eby6vVoHuFk0GFqxj uscuxrxtSMFxXtwBHobuG9nGXJVuAf0WO0xQUWWn2ikfZgvLWn3kzxtBy/vi8vnD 7K3IeBuamFo8rzixGtv0U7kXhcnpT83UpAcr2WxrMo/pJwednPZM =Gc9Z -----END PGP SIGNATURE----- --Sig_/8_/KV1nqqQOtqpC05WlGfe.-- From owner-freebsd-ports@freebsd.org Tue Oct 3 08:58:12 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 996A6E35C54 for ; Tue, 3 Oct 2017 08:58:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 854696B418 for ; Tue, 3 Oct 2017 08:58:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8459FE35C52; Tue, 3 Oct 2017 08:58:12 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 840EEE35C51 for ; Tue, 3 Oct 2017 08:58:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 75E056B417 for ; Tue, 3 Oct 2017 08:58:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v938wCKK087457 for ; Tue, 3 Oct 2017 08:58:12 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v938wC2Q087456; Tue, 3 Oct 2017 08:58:12 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201710030858.v938wC2Q087456@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 3 Oct 2017 08:58:12 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 08:58:12 -0000 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/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/aws-sdk-cpp | 1.2.5 | 1.2.6 ------------------------------------------------+-----------------+------------ lang/kawa | 2.4 | 3.0 ------------------------------------------------+-----------------+------------ 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 Thanks. From owner-freebsd-ports@freebsd.org Tue Oct 3 09:12:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02CA3E36684 for ; Tue, 3 Oct 2017 09:12:40 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D84466BE9F; Tue, 3 Oct 2017 09:12:39 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 2B7432DBB; Tue, 3 Oct 2017 09:12:39 +0000 (UTC) From: Jan Beich To: Kurt Jaeger Cc: Andrea Venturoli , freebsd-ports@FreeBSD.org Subject: Re: FireFox memory usage References: <20170915133803.GA2170@home.opsec.eu> Date: Tue, 03 Oct 2017 11:12:34 +0200 In-Reply-To: <20170915133803.GA2170@home.opsec.eu> (Kurt Jaeger's message of "Fri, 15 Sep 2017 15:38:03 +0200") Message-ID: <3770-tx19-wny@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 09:12:40 -0000 Kurt Jaeger writes: > Hi! > >> Since a few days my 4GiB desktop is crawling due to swap usage and >> looking at top, I see FireFox using almost 7GiB of RAM (SIZE column), >> 2.5 of which are "RES". > > Firefox memory usage grows without bounds, depending on the > websites you visit. I do not close my browser, it sometimes > runs for several months. It can easily consume 5-7 GB with > approx. 50 open browser windows. Maybe check if Firefox 57 (see bug 222693) improves memory usage to rule out legacy extensions with layers of e10s compatibility shims. > That's an issue the mozilla foundation should work on... Neither Mozilla Foundation nor FreeBSD Foundation directly support Firefox on FreeBSD. However, even with only volunteers things get fixed sometimes as long as someone files a bug. From owner-freebsd-ports@freebsd.org Tue Oct 3 10:43:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4F41E38160; Tue, 3 Oct 2017 10:43:34 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB0B46E592; Tue, 3 Oct 2017 10:43:34 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dzKfd-0001tg-Kn; Tue, 03 Oct 2017 12:43:25 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1dzKfd-0004KK-Ik; Tue, 03 Oct 2017 12:43:25 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Tue, 03 Oct 2017 10:43:25 GMT From: "Jeffrey Bouquet" To: "O. Hartmann" CC: "FreeBSD CURRENT" , "FreeBSD Ports" Subject: Re: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64? Date: Tue, 03 Oct 2017 03:43:25 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> Message-Id: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 10:43:35 -0000 On Tue, 3 Oct 2017 10:51:24 +0200, "O. Hartmann" w= rote: > When using "poudriere", it seems ABI is freebsd:12:x86:64. When using Fre= eBSD base, it > seems always to be referred to FreeBSD:12:amd64. What now? All non-BSD wo= rld uses x86:64, > FreeBSD is using amd64, but why is this used inconsistently all over the = places? >=20 > I run into trouble setting up some package- and base-servers and ran into= the problem > when deleting - not thinking of this discovered inconsistency - some link= s on the servers > regarding FreeBSD:12:x86:64 (the same is for 11-STABLE). >=20 > Can someone shed some light onto this?=20 >=20 > What am I supposed to use now? The handbook referes to amd64, so I though= t poudriere > would, too.=20 >=20 > Thanks in advance, >=20 > oh > --=20 > O. Hartmann >=20 > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Ab= s. 4 BDSG). [ not using poudriere yet ] /me too I think three places [ etc/pkg, /usr/local/etc/pkg/repos, 2nd place in base= , ] fourth: hard coded DESPITE the above in the current DB in var/db/pkg? fifth: derived somehow from uname -a? here: freebsd:12:x86:32 ... when this issue resolved, could it please be added to 'man pkg|poudrier= e|syntch|portmaster?|portupgrade? [ the latter two when developed further = ]'= From owner-freebsd-ports@freebsd.org Tue Oct 3 11:08:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B59FEE38A60; Tue, 3 Oct 2017 11:08:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B0FE6F234; Tue, 3 Oct 2017 11:08:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dzL4H-0006SV-Uv; Tue, 03 Oct 2017 13:08:53 +0200 Date: Tue, 3 Oct 2017 13:08:53 +0200 From: Kurt Jaeger To: "O. Hartmann" Cc: FreeBSD CURRENT , FreeBSD Ports Subject: Re: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64? Message-ID: <20171003110853.GO86601@home.opsec.eu> References: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 11:08:54 -0000 Hi! > When using "poudriere", it seems ABI is freebsd:12:x86:64. Where do you get that value from ? If I access a repo, I access e.g. https://repo.opsec.eu/${ABI} and ABI maps to FreeBSD:12:amd64 -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Tue Oct 3 12:04:20 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 412F1E3A7EC; Tue, 3 Oct 2017 12:04:20 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A115C714C0; Tue, 3 Oct 2017 12:04:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.192.150]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MbKXI-1dimTz1oAO-00Ijxl; Tue, 03 Oct 2017 14:04:07 +0200 Date: Tue, 3 Oct 2017 14:03:59 +0200 From: "O. Hartmann" To: Kurt Jaeger Cc: "O. Hartmann" , FreeBSD CURRENT , FreeBSD Ports Subject: Re: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64? Message-ID: <20171003140359.1d2a477e@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20171003110853.GO86601@home.opsec.eu> References: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> <20171003110853.GO86601@home.opsec.eu> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/icgBS3Hmy3sqq1+LmbsYnTw"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:HsnYvhTLG0B/kf0o7k+2N3dPmb4LeSAqeAn3Yr8lotRS5n2XXdA ltj94Be28VBJYftM1QWcM8JzmZ6sGYRnCoftliHP+8YFD/wKyn85Huc6WoZjL2GioOZf4u3 r+wPXITDcGs1dam36OezWelHFkMwJjZFa/XgkTPi4XomXVt03h7RT4nxIaFdzhJxLY6+C+T xCR4hQi/AZn4312El//tA== X-UI-Out-Filterresults: notjunk:1;V01:K0:uYT23rge5/Q=:N7r4agOIphrFZJufyNFHUK XUmttk1hpFeRZa0r6FiSDIlrGdwfLGL3Nq5oKKQ4QGJO6aSZAlJ2gEL4np+C6/N+G0doaYEFW 73lZVgfUpQu25ccEJnoEL6EJTRXm5o03HmU/7Sr2x5ug7s/s+yiQaHvD+t3FdPHjOOlIWO/vc RPhoh4qUUd9USc9l6/6qsEZXbgULJr7VsLlPzCA7SuvtgikotxaYTUnVJCUx7GkOqfQ1m6dIU YJmFJnYXc+a07yKWBgDPf9NWgiTn1muzfD//jLAucDuX4TW4USdU+VjI3b9+oHPHC0Mgk4bJX QZxOGr2zAygRI//T7Y1jlpb6+dt2lREgDsBYEva+Tf63iCrB5jC2rZerLbGj3XxPvCKYMzge7 m32CD1QYc7lo6BnuMVx1A7oZc/Hn5lBhU9AZPM7rHOXcvf8O90vRf44W1vhqFCABru5/KATLB GvjoUhLLaYQd0iOsT3YUCTiyFRJpYM5AZ9IpDkCHbJSuco0qK0RwgI75O1jZhHD+h6jGY5tz2 GT+4v74mi6RZMQUeHytmfrsvz7UwMSp0wWOfGFzv28565wfnllzpKDbN7tGT3eGaP6OumyBlR fWf4ZHQvDh5fRTF5LH0cU1Up2q9nA0nLjEQUJatZB4s9LHEg5AOtbdFM7Z5Q7qfwMfHggvu1v os5J9Ejp4Tq6UcwdyhJU9Mm6MxEhny7cu28jssUKk0YadwIT9l/yRLOTGVqGLSz81wLDmfoKL L+tIP+P/2H01udMYXhPi4XYvbhuchf768kadBDk7DHX31OkK1VRlvU+NPdIJmUFueeYofe3ir gyYtTOM04iiG6lrexVsgsGqEQLLAw== X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 12:04:20 -0000 --Sig_/icgBS3Hmy3sqq1+LmbsYnTw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Tue, 3 Oct 2017 13:08:53 +0200 Kurt Jaeger schrieb: > Hi! >=20 > > When using "poudriere", it seems ABI is freebsd:12:x86:64. =20 As I wrote: poudriere repo. >=20 > Where do you get that value from ? If I access a repo, > I access e.g. >=20 > https://repo.opsec.eu/${ABI} >=20 > and ABI maps to >=20 > FreeBSD:12:amd64 >=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/icgBS3Hmy3sqq1+LmbsYnTw Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWdN8rwAKCRDS528fyFhY lFjTAf9UbzaQuXUqb9+jKbivKZGzZy2IBCX7eqD693gt5mlqVHpiJ4GThKgfxEPs irMFCfTaJtVWLxybzWVZ3pfsa9rYAf93+4oJcx0GdopBp72bWS0VgkvklQPXsxuO fe5cXBLZPMXe+ULGWLVznia+R8rDbu6Lov1DnHMQrgFCmlMlY3Jn =9g/7 -----END PGP SIGNATURE----- --Sig_/icgBS3Hmy3sqq1+LmbsYnTw-- From owner-freebsd-ports@freebsd.org Tue Oct 3 12:06:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 891E8E3A961 for ; Tue, 3 Oct 2017 12:06:17 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CB36716F7 for ; Tue, 3 Oct 2017 12:06:16 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from leaf.local (unknown [88.202.132.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 9EEF0331D for ; Tue, 3 Oct 2017 12:06:13 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: ABI confusion: freebsd:12:x86:64 or ABI: freebsd:12:amd64? To: freebsd-ports@freebsd.org References: <20171003105124.6b661017@thor.intern.walstatt.dynvpn.de> <20171003110853.GO86601@home.opsec.eu> From: Matthew Seaman Message-ID: <9f463d6e-a232-12e1-329c-d49eb70dadde@FreeBSD.org> Date: Tue, 3 Oct 2017 13:06:13 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171003110853.GO86601@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 12:06:17 -0000 On 03/10/2017 12:08, Kurt Jaeger wrote: > Hi! > >> When using "poudriere", it seems ABI is freebsd:12:x86:64. > > Where do you get that value from ? If I access a repo, > I access e.g. > > https://repo.opsec.eu/${ABI} > > and ABI maps to > > FreeBSD:12:amd64 > There's history here. Originally in pkg(8) the ABI value looked like: freebsd:11:x86:64 then about 4 years ago the ABI value was switched to look like: FreeBSD:11:amd64 which is how it has remained to this day. I believe the motivation for this change was to bring the setting into line with the arch value used elsewhere in the system. The old value was still available as ALTABI -- mostly implemented as a transitional thing so we didn't unnecessarily cause too much grief by breaking loads of poudriere setups with local repositories. Oh, and the ALTABI value is still used internally to pkg(8) in a few places IIRC. The idea was that ALTABI would become redundant over time and could eventually be deleted. However, it seems that a new use has been found for it to do with packaged base and managing major version upgrades, so it will apparently be sticking around for the foreseeable future. Cheers, Matthew From owner-freebsd-ports@freebsd.org Tue Oct 3 16:19:03 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FE6CE4190D for ; Tue, 3 Oct 2017 16:19:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3AAE37FA96 for ; Tue, 3 Oct 2017 16:19:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 36AA7E4190C; Tue, 3 Oct 2017 16:19:03 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3451FE4190B; Tue, 3 Oct 2017 16:19:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 127537FA95; Tue, 3 Oct 2017 16:19:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-131-198.dyn.iinet.net.au [106.68.131.198]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v93GIp1m039818 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 3 Oct 2017 09:18:55 -0700 (PDT) (envelope-from julian@freebsd.org) To: "ports@FreeBSD.org" , freebsd-current From: Julian Elischer Subject: anyone know how to get rid of this error? (10.4/Gcc vs binutils port) Message-ID: <1889a630-f0c6-295d-4fda-8b843841b36d@freebsd.org> Date: Wed, 4 Oct 2017 00:18:46 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 16:19:03 -0000 Our 10.4 system is using gcc (for now). when we compile the devel/binutils port, we get a failure with a bunch of these errors: `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section `.rodata' of aarch64.o: defined in discarded section `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE[_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE]' of aarch64.o `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE' referenced in section `.rodata' of aarch64.o: defined in discarded section `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE[_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE]' of aarch64.o I managed to defeat these one before but I forget how. possibly the answer is to use clang/clang++ for this item but I tried defining CC and CXX  to clang/clang++ in the Makefile but that didn't seem to help there's probably a USE_CLANG option or something that I haven't seen. From owner-freebsd-ports@freebsd.org Tue Oct 3 16:48:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF540E422E1 for ; Tue, 3 Oct 2017 16:48:52 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp10.server.rpi.edu (gateway.canit.rpi.edu [128.113.2.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "canit.localdomain", Issuer "canit.localdomain" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B30BD80B2F for ; Tue, 3 Oct 2017 16:48:52 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp-auth2.server.rpi.edu (route.canit.rpi.edu [128.113.2.232]) by smtp10.server.rpi.edu (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id v93Gd8Ax017726 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 3 Oct 2017 12:39:08 -0400 Received: from smtp-auth2.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth2.server.rpi.edu (Postfix) with ESMTP id F2F481808C; Tue, 3 Oct 2017 12:39:07 -0400 (EDT) Received: from [172.16.67.1] (gilead-qc124.netel.rpi.edu [128.113.124.17]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drosih) by smtp-auth2.server.rpi.edu (Postfix) with ESMTPSA id E838718075; Tue, 3 Oct 2017 12:39:07 -0400 (EDT) From: "Garance A Drosehn" To: freebsd-ports@freebsd.org Subject: Re: Status of portupgrade and portmaster? Date: Tue, 03 Oct 2017 12:39:07 -0400 Message-ID: <970B517A-2E0C-4540-868D-11CBC0ED2F89@rpi.edu> In-Reply-To: References: <81D84A650858BA40BF6936408052E6BC0138263988@msgdb11.utad.utoledo.edu> <201709290909.v8T99QtU006095@mxdrop301.xs4all.net> MIME-Version: 1.0 X-Mailer: MailMate (1.9.7r5419) X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 10.10] X-CanIt-Incident-Id: 03Uh4D802 X-CanIt-Geo: ip=128.113.124.17; country=US; region=New York; city=Troy; latitude=42.7495; longitude=-73.5951; http://maps.google.com/maps?q=42.7495,-73.5951&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.230 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 16:48:53 -0000 On 29 Sep 2017, at 15:21, Marco Beishuizen wrote: > On Fri, 29 Sep 2017, the wise Thomas Mueller wrote: > >> What is the current status of portupgrade and portmaster? >> >> I haven't used portupgrade in some time, but what about portmaster? > > Using portupgrade every day and still works great. Tried portmaster > once but liked portupgrade more. I use poudriere just for testing > ports. FWIW, I still stick with portupgrade and am happy to continue using it. It works fine for my systems and the collection of ports that I use. Every 14-18 months some change comes up where I run into some significant headache with my ports, and when that happens I prefer to rebuild my entire ports collection from scratch. I do this in a chroot environment on that system, so I can start from scratch and build up a full collection without disrupting anything on my system. Once I have successfully build a brand new collection of ports, then I switch from my older ports-collection to the newly-rebuilt ports-collection. During one of those situations where my current ports-collection was experiencing problems, I made a serious effort to try poudriere. It did not work for me in that situation. And based on what I went through in that situation, I suspect it is not a good fit for my (few) freebsd systems. The problem is that I have only a few systems, and they are very different. (different major releases of FreeBSD, different hardware architectures, or significantly different sets of ports). I expect that if I had *more* systems, and if those systems were more similar, then poudriere would be a valuable tool for me. That's my own experience. I doubt it will convince anyone who has a different set of requirements than I do. -- Garance Alistair Drosehn = drosih@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-ports@freebsd.org Tue Oct 3 16:49:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CDEEE42306 for ; Tue, 3 Oct 2017 16:49:08 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7311F80BCC; Tue, 3 Oct 2017 16:49:08 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id CF16BBD2; Tue, 3 Oct 2017 11:49:00 -0500 (CDT) Date: Tue, 3 Oct 2017 11:48:59 -0500 From: Mark Linimon To: Julian Elischer Cc: Simon Wright , freebsd-ports@freebsd.org Subject: Re: gettng the port revision number associated with the pkg repo. [Please?) Message-ID: <20171003164859.GA2918@lonesome.com> References: <27a74475-e146-0cd4-e5ac-f59686317be9@freebsd.org> <44fub9d054.fsf@be-well.ilk.org> <66ef45c6-b448-c8fe-9686-10f0cab13ecb@freebsd.org> <447ewjarab.fsf@be-well.ilk.org> <60b690b5-d34d-56ea-a371-414d4dddaaaa@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 16:49:08 -0000 On Tue, Oct 03, 2017 at 01:29:23AM +0800, Julian Elischer wrote: > can we just find out who runs the poudriere instances and > ask them to just append the svn revision number somewhere? > or maybe even the poudriere commands  used.. http://www.freebsd.org/portmgr/ ; portmgr@FreeBSD.org Specifically, QA Policies, although due to staleness the page does not _specifically_ mention poudriere as the current technology. None of this is especially secret. mcl From owner-freebsd-ports@freebsd.org Tue Oct 3 16:56:19 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 135D0E425F8 for ; Tue, 3 Oct 2017 16:56:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id ED027810EE for ; Tue, 3 Oct 2017 16:56:18 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EC475E425F7; Tue, 3 Oct 2017 16:56:18 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBF09E425F6 for ; Tue, 3 Oct 2017 16:56:18 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF0F3810EC for ; Tue, 3 Oct 2017 16:56:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: c672136a-a85b-11e7-a937-4f970e858fdb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id c672136a-a85b-11e7-a937-4f970e858fdb; Tue, 03 Oct 2017 16:56:18 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v93GuALN001521; Tue, 3 Oct 2017 10:56:10 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507049770.86205.16.camel@freebsd.org> Subject: Re: anyone know how to get rid of this error? (10.4/Gcc vs binutils port) From: Ian Lepore To: Julian Elischer , "ports@FreeBSD.org" , freebsd-current Date: Tue, 03 Oct 2017 10:56:10 -0600 In-Reply-To: <1889a630-f0c6-295d-4fda-8b843841b36d@freebsd.org> References: <1889a630-f0c6-295d-4fda-8b843841b36d@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 16:56:19 -0000 On Wed, 2017-10-04 at 00:18 +0800, Julian Elischer wrote: > Our 10.4 system is using gcc (for now). > > when we compile the devel/binutils port, we get a failure with a > bunch  > of these errors: > > > `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section  > `.rodata' of aarch64.o: defined in discarded section  > `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE[_ZTSN12_GLOBAL__ > N_110Stub_tableILi64ELb1EEE]'  > of aarch64.o > `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE' referenced in section  > `.rodata' of aarch64.o: defined in discarded section  > `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE[_ZTSN12_GLOBAL__ > N_110Stub_tableILi64ELb0EEE]'  > of aarch64.o > > > I managed to defeat these one before but I forget how. > > possibly the answer is to use clang/clang++ for this item but I > tried  > defining CC and CXX  to clang/clang++ in the Makefile but that > didn't  > seem to help > > there's probably a USE_CLANG option or something that I haven't seen. We ran into the same thing recently at $work.  The root cause for us involved having same-named classes in anonymous namespaces in different compilation units.  The classes made reference to something that was declared extern "C", bringing into play some rules about how C things in anon namespaces really refer to the same global C object outside of any namespace.  Then link-time optimization led to discarding the object from one compilation unit, and that somehow resulted in discarding the referenced extern "C" thing completely, even though it was still referenced from the non-discarded instance of an object from a different compilation unit.  Phew. The same code has no problems with clang on freebsd 11, just with gcc on 10.3.   So, for us the fix was a bit heavy-handed: we just renamed one of the classes involved in the problem so that there were no longer any same- named classes in anon namespaces in separate compilation units.  Probably not a good option for you.  A fix involving compile options might result in not discarding unreferenced segments at all, and with templated code that might result in huge binaries. Mixing clang-compiled and gcc-compiled c++ may give you grief with exceptions and other things (it would on ARM on 10.x, but maybe not on x86 arches). -- Ian From owner-freebsd-ports@freebsd.org Tue Oct 3 17:07:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56865E42B2F for ; Tue, 3 Oct 2017 17:07:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4129781957 for ; Tue, 3 Oct 2017 17:07:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 405A0E42B2E; Tue, 3 Oct 2017 17:07:36 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DE69E42B2D; Tue, 3 Oct 2017 17:07:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F7AD81956; Tue, 3 Oct 2017 17:07:35 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-68-131-198.dyn.iinet.net.au [106.68.131.198]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v93H7T5K040003 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 3 Oct 2017 10:07:32 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: anyone know how to get rid of this error? (10.4/Gcc vs binutils port) To: Ian Lepore , "ports@FreeBSD.org" , freebsd-current References: <1889a630-f0c6-295d-4fda-8b843841b36d@freebsd.org> <1507049770.86205.16.camel@freebsd.org> From: Julian Elischer Message-ID: Date: Wed, 4 Oct 2017 01:07:23 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1507049770.86205.16.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 17:07:36 -0000 On 4/10/17 12:56 am, Ian Lepore wrote: > On Wed, 2017-10-04 at 00:18 +0800, Julian Elischer wrote: >> Our 10.4 system is using gcc (for now). >> >> when we compile the devel/binutils port, we get a failure with a >> bunch >> of these errors: >> >> >> `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section >> `.rodata' of aarch64.o: defined in discarded section >> `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE[_ZTSN12_GLOBAL__ >> N_110Stub_tableILi64ELb1EEE]' >> of aarch64.o >> `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE' referenced in section >> `.rodata' of aarch64.o: defined in discarded section >> `.rodata._ZTSN12_GLOBAL__N_110Stub_tableILi64ELb0EEE[_ZTSN12_GLOBAL__ >> N_110Stub_tableILi64ELb0EEE]' >> of aarch64.o >> >> >> I managed to defeat these one before but I forget how. >> >> possibly the answer is to use clang/clang++ for this item but I >> tried >> defining CC and CXX  to clang/clang++ in the Makefile but that >> didn't >> seem to help >> >> there's probably a USE_CLANG option or something that I haven't seen. > We ran into the same thing recently at $work.  The root cause for us > involved having same-named classes in anonymous namespaces in different > compilation units.  The classes made reference to something that was > declared extern "C", bringing into play some rules about how C things > in anon namespaces really refer to the same global C object outside of > any namespace.  Then link-time optimization led to discarding the > object from one compilation unit, and that somehow resulted in > discarding the referenced extern "C" thing completely, even though it > was still referenced from the non-discarded instance of an object from > a different compilation unit.  Phew. > > The same code has no problems with clang on freebsd 11, just with gcc > on 10.3. > > So, for us the fix was a bit heavy-handed: we just renamed one of the > classes involved in the problem so that there were no longer any same- > named classes in anon namespaces in separate compilation units. >  Probably not a good option for you.  A fix involving compile options > might result in not discarding unreferenced segments at all, and with > templated code that might result in huge binaries. > > Mixing clang-compiled and gcc-compiled c++ may give you grief with > exceptions and other things (it would on ARM on 10.x, but maybe not on > x86 arches). > > -- Ian > > thanks the issue comes up in the binutils port which is a dependency of gdb. I don't think we actually need to install the binutils port on our appliance, (and we only install gdb to generate backtraces on debug reports) I just added CC=clang and CXX=clang++ in the makefile that called it and the problem seemed to go away. All i wanted to do is get gdb compiled and I end up with gcc6, llvm and binutils (plus a whole lot more) as a bonus (plus an extra 30 minutes of compile time) From owner-freebsd-ports@freebsd.org Wed Oct 4 06:05:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21DAEE2F521 for ; Wed, 4 Oct 2017 06:05:52 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0378472FB4 for ; Wed, 4 Oct 2017 06:05:52 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by mailman.ysv.freebsd.org (Postfix) id F34D7E2F520; Wed, 4 Oct 2017 06:05:51 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFA30E2F51F for ; Wed, 4 Oct 2017 06:05:51 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail.stromnet.se (s0.stromnet.se [109.74.15.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F8B172FB3 for ; Wed, 4 Oct 2017 06:05:50 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail (mail.j.stromnet.se [172.28.10.1]) by mail.stromnet.se (Postfix) with ESMTP id AE458D7A4F; Wed, 4 Oct 2017 07:59:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=stromnet.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=default; t=1507096782; bh=bNTWlxDf+fj+BgceWDPm3R0Ab H4NsTW9UqkID7HyFuU=; b=SffSoRvQB1fpwrtiUoEaPRiwTiGnDRa7O+bqrA+gk lmQOWkqx4M0gqFA+GLugB0fIY306Py5xU/IHVsJBil+Sh3KtSAmuxw/pAjwaNFi5 abzuZZdQGmiaH5+B+FpfPhXmhfjtIB1F8nFJzpJOntbUgHTcXjaoBzT9AYUiE/54 SlOWKOUqGlG8OyuEA4A5j3f7XmzwhtH6zRneCh9m+4Ej+hqAa4KGdiGewbCnnJbp FD+ecaKfLfrhOk4ywb5g9se/nFFbvp4pTdv9DvkTffuPlD9HLfCuXrs4mJDrKeqz QIcQ2rLQA7lC/Of6BiDOba5LTwJ4eoO5qPATAGmNfSBuQ== X-Virus-Scanned: amavisd-new at stromnet.se Received: from mail.stromnet.se ([172.28.10.1]) by mail (mail.stromnet.se [172.28.10.1]) (amavisd-new, port 10026) with ESMTP id Rekra1WrwfIL; Wed, 4 Oct 2017 07:59:42 +0200 (CEST) Received: from johan-ht.stromnet.se (c-abfa70d5.019-333-67626721.cust.bredbandsbolaget.se [213.112.250.171]) by mail.stromnet.se (Postfix) with ESMTPSA id A6905D7990; Wed, 4 Oct 2017 07:59:42 +0200 (CEST) Subject: Re: FreeBSD telldusd port fix for devd script To: Hans Petter Selasky References: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> From: =?UTF-8?Q?Johan_Str=c3=b6m?= Cc: ports@FreeBSD.org Message-ID: <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> Date: Wed, 4 Oct 2017 07:59:42 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 06:05:52 -0000 Hi, thanks, verified and seems to work fine, at least on unplug/re-plug. I added a "logger "logger ATTACH event on $cdev;" to the action too. On unplug-plug scenario this was logged and all worked fine [1]. On a reboot it did not log it [2], but it actually seems to have executed, as the dialer group have been set on ugen0.2 and telldusd is able to interact with it. Can I expect that this will execute on system boot too, or is there some other magic involved for that? logger not ready for use at that stage, but devd is perhaps? Johan 1. Device inserted Oct=C2=A0 4 07:43:48 back-1 kernel: ugen0.2: at usbus0 Oct=C2=A0 4 07:43:48 back-1 kernel: uftdi0: on usbus0 Oct=C2=A0 4 07:43:48 back-1 devd: Executing 'logger ATTACH event on ugen0= .2; chgrp dialer /dev/ugen0.2; chmod 660 /dev/ugen0.2 /usr/local/sbin/tdadmin --pid 0x0c30 --vid 0x1781 --serial A6008W8a controller connect' Oct=C2=A0 4 07:43:48 back-1 johan: ATTACH event on ugen0.2 ... Oct=C2=A0 4 07:44:17 back-1 telldusd: Connecting to TellStick (1781/C30) = with serial A6008W8a 2. System boot with device already plugged in Oct=C2=A0 4 07:49:12 back-1 kernel: ugen0.2: at usbus0 ... Oct=C2=A0 4 07:49:12 back-1 kernel: uftdi0: on usbus0 ... Oct=C2=A0 4 07:49:34 back-1 telldusd: Connecting to TellStick (1781/C30) = with serial A6008W8a But nothing from devd or ATTACH event. On 30/09/17 21:07, Hans Petter Selasky wrote: > Hi Johan, > > The following devd script is not fully correct. > >> --- tdadmin/freebsd-devd-tellstick.conf=C2=A0=C2=A0=C2=A0 2014-04-06 >> 22:40:11.000000000 +0200 >> +++ tdadmin/freebsd-devd-tellstick.conf=C2=A0=C2=A0=C2=A0 2014-04-06 >> 20:37:50.501751596 +0200 >> @@ -0,0 +1,12 @@ >> +attach 10 { >> +=C2=A0=C2=A0=C2=A0 device-name "uftdi[0-9]+"; >> +=C2=A0=C2=A0=C2=A0 match "vendor" "0x1781"; >> +=C2=A0=C2=A0=C2=A0 match "product" "0x0c30"; >> + >> +=C2=A0=C2=A0=C2=A0 action "chgrp dialer /dev/ugen$port.$devaddr; chmo= d 660 >> /dev/ugen$port.$devaddr; >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @CMAKE_INSTALL_PREFIX@/sbi= n/tdadmin --pid $product --vid >> $vendor --serial $sernum controller connect"; >> +}; > > It should be: > > notify 10 { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 match "system" "USB"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 match "subsystem" "DEVICE"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 match "type" "ATTACH"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 match "vendor" "0x1781"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 match "product" "0x0c30"; > =C2=A0=C2=A0=C2=A0=C2=A0action "chgrp dialer /dev/$cdev; chmod 660 /dev= /$cdev > @CMAKE_INSTALL_PREFIX@/sbin/tdadmin --pid $product --vid $vendor > --serial $sernum controller connect"; > } > > Can you test and update the port in FreeBSD ? > > Thank you! > > --HPS From owner-freebsd-ports@freebsd.org Wed Oct 4 08:06:01 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8FC4E320C4 for ; Wed, 4 Oct 2017 08:06:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D40FB76B59 for ; Wed, 4 Oct 2017 08:06:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id D33E6E320C1; Wed, 4 Oct 2017 08:06:01 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2D60E320C0 for ; Wed, 4 Oct 2017 08:06:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F7D376B58 for ; Wed, 4 Oct 2017 08:06:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D837C260164; Wed, 4 Oct 2017 10:05:56 +0200 (CEST) Subject: Re: FreeBSD telldusd port fix for devd script To: =?UTF-8?Q?Johan_Str=c3=b6m?= Cc: ports@FreeBSD.org References: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> From: Hans Petter Selasky Message-ID: <7bdad62d-4897-c4ff-6e7a-c5362ccc131c@selasky.org> Date: Wed, 4 Oct 2017 10:03:21 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 08:06:02 -0000 On 10/04/17 07:59, Johan Ström wrote: > Hi, > > thanks, verified and seems to work fine, at least on unplug/re-plug. > > I added a "logger "logger ATTACH event on $cdev;" to the action too. On > unplug-plug scenario this was logged and all worked fine [1]. > On a reboot it did not log it [2], but it actually seems to have > executed, as the dialer group have been set on ugen0.2 and telldusd is > able to interact with it. > > Can I expect that this will execute on system boot too, or is there some > other magic involved for that? logger not ready for use at that stage, > but devd is perhaps? Yes, but it is not executed until the devd is started. All the events are queued in the kernel and then when devd opens they are read and executed. --HPS From owner-freebsd-ports@freebsd.org Wed Oct 4 09:11:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85337E33640 for ; Wed, 4 Oct 2017 09:11:27 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6925B7CA9D for ; Wed, 4 Oct 2017 09:11:27 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 68945E3363F; Wed, 4 Oct 2017 09:11:27 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 683B2E3363E for ; Wed, 4 Oct 2017 09:11:27 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A3387CA9C for ; Wed, 4 Oct 2017 09:11:27 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v949BRpJ030937 for ; Wed, 4 Oct 2017 09:11:27 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v949BR38030927; Wed, 4 Oct 2017 09:11:27 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201710040911.v949BR38030927@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Wed, 4 Oct 2017 09:11:27 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 09:11:27 -0000 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/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/aws-sdk-cpp | 1.2.5 | 1.2.7 ------------------------------------------------+-----------------+------------ 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 Thanks. From owner-freebsd-ports@freebsd.org Wed Oct 4 14:30:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DCF5E3AB67 for ; Wed, 4 Oct 2017 14:30:17 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id F28296419A for ; Wed, 4 Oct 2017 14:30:16 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by mailman.ysv.freebsd.org (Postfix) id E7A41E3AB65; Wed, 4 Oct 2017 14:30:16 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7456E3AB64 for ; Wed, 4 Oct 2017 14:30:16 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail.stromnet.se (s0.stromnet.se [109.74.15.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E4EB64199 for ; Wed, 4 Oct 2017 14:30:15 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail (mail.j.stromnet.se [172.28.10.1]) by mail.stromnet.se (Postfix) with ESMTP id 4170BD79D5; Wed, 4 Oct 2017 16:30:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=stromnet.se; h= message-id:from:from:subject:subject:content-transfer-encoding :content-type:content-type:mime-version:references:in-reply-to :user-agent:date:date:received:received; s=default; t= 1507127409; bh=N9xVdJAd6/+snn0ki7i+bX7zYN9kmEhOXazkYihn440=; b=u bvD55pdK7M5ZFuMpmws3KOojLvmQHWTBt/2s0dS5JICKbb3ekvQuG9qYzLdQN+zu UivYRALBkyI7YIsCCqnPGu2AzLbjvXvlZDYdeDxOaBZRB4qwb1kZQep1jED3hfKD a8teUTgFJjW0KTv2E7o8nmDrAWfv5NfwhbEijFpqN2k3N9n0HIT3ZqM9fTYjtEFD Bqy/4mV+GUICVOcM20o76/pM4GZRNP6bA+rP1I8jEyktiDtahI1uXIE0mQ0aj7rl pkpLXioNbbnBjZx0mbga2t4MOBxuie62167cDGNoO5xD1WzNZQJedOz1Qds8yHUZ /8parZopwGF3FV/vfiV5w== X-Virus-Scanned: amavisd-new at stromnet.se Received: from mail.stromnet.se ([172.28.10.1]) by mail (mail.stromnet.se [172.28.10.1]) (amavisd-new, port 10026) with ESMTP id XyIujNyWeI1s; Wed, 4 Oct 2017 16:30:09 +0200 (CEST) Received: from [100.80.194.191] (m83-185-242-191.cust.tele2.se [83.185.242.191]) by mail.stromnet.se (Postfix) with ESMTPSA id D6208D796A; Wed, 4 Oct 2017 16:30:08 +0200 (CEST) Date: Wed, 04 Oct 2017 16:30:07 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <7bdad62d-4897-c4ff-6e7a-c5362ccc131c@selasky.org> References: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> <7bdad62d-4897-c4ff-6e7a-c5362ccc131c@selasky.org> MIME-Version: 1.0 Subject: Re: FreeBSD telldusd port fix for devd script To: Hans Petter Selasky CC: ports@FreeBSD.org From: =?ISO-8859-1?Q?Johan_Str=F6m?= Message-ID: <03E2E2EC-85B6-4597-8F53-12B7E4F083F5@stromnet.se> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 14:30:17 -0000 Ah, okay=2E Well, it works now and didn't work with the old devd rule, I'm = happy with that :) Shall I create a patch and submit to bugzilla, or are you fixing this as p= art of bigger cleanup? On October 4, 2017 10:03:21 AM GMT+02:00, Hans Petter Selasky wrote: >On 10/04/17 07:59, Johan Str=C3=B6m wrote: >> Hi, >>=20 >> thanks, verified and seems to work fine, at least on unplug/re-plug=2E >>=20 >> I added a "logger "logger ATTACH event on $cdev;" to the action too=2E >On >> unplug-plug scenario this was logged and all worked fine [1]=2E >> On a reboot it did not log it [2], but it actually seems to have >> executed, as the dialer group have been set on ugen0=2E2 and telldusd >is >> able to interact with it=2E >>=20 >> Can I expect that this will execute on system boot too, or is there >some >> other magic involved for that? logger not ready for use at that >stage, >> but devd is perhaps? > >Yes, but it is not executed until the devd is started=2E All the events= =20 >are queued in the kernel and then when devd opens they are read and=20 >executed=2E > >--HPS --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-ports@freebsd.org Wed Oct 4 14:53:57 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45290E3B54D for ; Wed, 4 Oct 2017 14:53:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2F810652E9 for ; Wed, 4 Oct 2017 14:53:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2B8A4E3B54C; Wed, 4 Oct 2017 14:53:57 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B1D7E3B54B for ; Wed, 4 Oct 2017 14:53:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9EA3652E8 for ; Wed, 4 Oct 2017 14:53:56 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A57D12601AB; Wed, 4 Oct 2017 16:53:54 +0200 (CEST) Subject: Re: FreeBSD telldusd port fix for devd script To: =?UTF-8?Q?Johan_Str=c3=b6m?= Cc: ports@FreeBSD.org References: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> <7bdad62d-4897-c4ff-6e7a-c5362ccc131c@selasky.org> <03E2E2EC-85B6-4597-8F53-12B7E4F083F5@stromnet.se> From: Hans Petter Selasky Message-ID: <13c93a08-ecf0-fd4a-3a7b-3ba74c54d35b@selasky.org> Date: Wed, 4 Oct 2017 16:51:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <03E2E2EC-85B6-4597-8F53-12B7E4F083F5@stromnet.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 14:53:57 -0000 On 10/04/17 16:30, Johan Ström wrote: > Ah, okay. Well, it works now and didn't work with the old devd rule, I'm happy with that :) > > Shall I create a patch and submit to bugzilla, or are you fixing this as part of bigger cleanup? Please submit it straight to ports. No more cleanup from my side at the present. telldus is working great btw 24/7 ! --HPS From owner-freebsd-ports@freebsd.org Wed Oct 4 14:57:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09B03E3B697 for ; Wed, 4 Oct 2017 14:57:41 +0000 (UTC) (envelope-from gabergt87@virgilio.it) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E9F0F65423 for ; Wed, 4 Oct 2017 14:57:40 +0000 (UTC) (envelope-from gabergt87@virgilio.it) Received: by mailman.ysv.freebsd.org (Postfix) id E958CE3B696; Wed, 4 Oct 2017 14:57:40 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E904FE3B695 for ; Wed, 4 Oct 2017 14:57:40 +0000 (UTC) (envelope-from gabergt87@virgilio.it) Received: from libero.it (smtp-31-vd.italiaonline.it [213.209.8.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7BBB66541D for ; Wed, 4 Oct 2017 14:57:39 +0000 (UTC) (envelope-from gabergt87@virgilio.it) Received: from service-mail-clu1-node4.iol.local ([10.255.27.209]) by smtp-31.iol.local with SMTP id zl7Bd8pcDykKtzl7Bd8Ysf; Wed, 04 Oct 2017 16:57:37 +0200 x-libjamoibt: 1601 From: Mr Jimmy Johnson Sender: Giga Mail Reply-To: Mr Jimmy Johnson To: Message-ID: <20653705.2439789.1507129057287.JavaMail.httpd@service-mail-clu1-node4> Subject: Please do not forget to reply me on this E-mail(diplomaticagent96197@yahoo.com) X-CP-HugEmail-A: 4CQKJUZPCJTVW2AQVU2VWSOB X-CP-HugEmail-B: 4b48534140462d MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Wed, 04 Oct 2017 14:57:41 -0000 X-List-Received-Date: Wed, 04 Oct 2017 14:57:41 -0000 From owner-freebsd-ports@freebsd.org Wed Oct 4 16:16:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4A91E3D053 for ; Wed, 4 Oct 2017 16:16:52 +0000 (UTC) (envelope-from mwlucas@mail.michaelwlucas.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AD4436821F for ; Wed, 4 Oct 2017 16:16:52 +0000 (UTC) (envelope-from mwlucas@mail.michaelwlucas.com) Received: by mailman.ysv.freebsd.org (Postfix) id A97E6E3D052; Wed, 4 Oct 2017 16:16:52 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8ECFE3D051 for ; Wed, 4 Oct 2017 16:16:52 +0000 (UTC) (envelope-from mwlucas@mail.michaelwlucas.com) Received: from mail.michaelwlucas.com (mail.michaelwlucas.com [104.236.197.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 716E56821E for ; Wed, 4 Oct 2017 16:16:52 +0000 (UTC) (envelope-from mwlucas@mail.michaelwlucas.com) Received: from mail.michaelwlucas.com (localhost [127.0.0.1]) by mail.michaelwlucas.com (8.15.2/8.15.2) with ESMTP id v94GGn80051990 for ; Wed, 4 Oct 2017 12:16:49 -0400 (EDT) (envelope-from mwlucas@mail.michaelwlucas.com) Received: (from mwlucas@localhost) by mail.michaelwlucas.com (8.15.2/8.15.2/Submit) id v94GGnIs051989 for ports@freebsd.org; Wed, 4 Oct 2017 12:16:49 -0400 (EDT) (envelope-from mwlucas) Date: Wed, 4 Oct 2017 12:16:49 -0400 From: "Michael W. Lucas" To: ports@freebsd.org Subject: portmaster, portupgrade, etc Message-ID: <20171004161649.GA51883@mail.michaelwlucas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.michaelwlucas.com X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mail.michaelwlucas.com [127.0.0.1]); Wed, 04 Oct 2017 12:16:50 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 16:16:52 -0000 Hi, I'm doing tech edits on the new edition of "Absolute FreeBSD," and stumbled into what's apparently a delicate topic. Some of my reviewers are happy I included portmaster in the book. Some reviewers beg me not to include it. Unfortunately, people will be reading af3e and considering it definitive for the next several years. So I have to get a feel for where things are going. :-/ I've read a couple threads on portmaster's current problems/growing pains and its looming difficulty with forthcoming flavors. I've been a happy portmaster user for many years now. All things being equal, if its future is still being debated I'm inclined to keep it in the book. Poudriere really needs its own small book. Yes, you can do simple poudriere installs, but once you start covering it properly the docs quickly expand. My notes alone are longer than my af3e chapter limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in 2018). Truly, I'm not looking to start a flame war here. I only want a bit of guidance on The Future... ==ml -- Michael W. Lucas https://mwl.io/ nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ From owner-freebsd-ports@freebsd.org Wed Oct 4 16:58:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0937E3DEAF for ; Wed, 4 Oct 2017 16:58:40 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 921FC69CB5 for ; Wed, 4 Oct 2017 16:58:40 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id v94GwDxS013771 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 4 Oct 2017 12:58:18 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> From: George Mitchell Message-ID: Date: Wed, 4 Oct 2017 12:58:07 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KF88FBObOxPaX6uUP9Pm60W6nJmiaawh9" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Wed, 04 Oct 2017 12:58:20 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 16:58:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KF88FBObOxPaX6uUP9Pm60W6nJmiaawh9 Content-Type: multipart/mixed; boundary="8nd0Uea03OqrHI09ULwMjFCxjmNjNdJN2"; protected-headers="v1" From: George Mitchell To: freebsd-ports@freebsd.org Message-ID: Subject: Re: portmaster, portupgrade, etc References: <20171004161649.GA51883@mail.michaelwlucas.com> In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> --8nd0Uea03OqrHI09ULwMjFCxjmNjNdJN2 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/04/17 12:16, Michael W. Lucas wrote: > Hi, >=20 > I'm doing tech edits on the new edition of "Absolute FreeBSD," and > stumbled into what's apparently a delicate topic. >=20 > Some of my reviewers are happy I included portmaster in the book. >=20 > Some reviewers beg me not to include it. [...] It's hard to guess where things are going at the moment. You can count me among the happy users of portmaster; and I generally incline toward the view that more information is better than less. -- George --8nd0Uea03OqrHI09ULwMjFCxjmNjNdJN2-- --KF88FBObOxPaX6uUP9Pm60W6nJmiaawh9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlnVEx8ACgkQwRES3m+p 4flxAQ//WCpE15zWPpwn3UOkQ3OjL3UlU1cB1TJJwcOUh2QNqEcB1v817mQIKZ7w gfp/okztkaZ4C0DYtlsXoBMya9PU4jtkjq58YN0J7VezLOEHeYeyCeWYPz41eG3T F5JyAnbe6LpyTDghCwHujA3AjOgA17dyaR02989jWWOU+zii+0r5igs1SPYR/ozx 1q+W6th9b2OJb/ucEE8+Gb9xs+MpSn60Bpv5AF5ysyEzeCyLOns+v0ZcNdDnW7tq CYqmYiJuV8l87CCb530jApPqsTy7mjK1+f7CSoLgQL1LJPMdzC0ncAZzl2kKkAF9 yMqqeQd4Wkoj9hd8B9L6h2ME7MVgQ3nmHxFHDDGuOJEH+jSfkNyZ8WxU5qTW2OgH UwhJS2YEEvLtj7feVtQQqf7cTs0p0Jk+pmDYkgUFbdyAXBvtnQaegbgJ1/J1pIVH O8QuC/9DAjEcEEbHW/kis/n2lWHGA0Mn3WQTUd1ogW8gYJczelGt+q6rR9ooiu1f IZjXiyfEuGD9O9bboUvntDgUCzbMyqiFsVUCfKZ0SNy9UcjqTm7NcroRAlDGJRdg GRkSwg2KmOflkosIZp5oMHDrVt1zVT4CFK1TSXUVso+DoMCuWPobYtQD9vZ6hEUN KF7KNkJyHT+2eluicENNy5+h/eS+5mUR13t2ao8vSm6O7pLotYQ= =weZ9 -----END PGP SIGNATURE----- --KF88FBObOxPaX6uUP9Pm60W6nJmiaawh9-- From owner-freebsd-ports@freebsd.org Wed Oct 4 17:15:25 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B28D5E3E5CB for ; Wed, 4 Oct 2017 17:15:25 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9C4786A76B for ; Wed, 4 Oct 2017 17:15:25 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 9B8E5E3E5CA; Wed, 4 Oct 2017 17:15:25 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B2C8E3E5C9 for ; Wed, 4 Oct 2017 17:15:25 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 812C46A76A for ; Wed, 4 Oct 2017 17:15:25 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v94HFIVp022553 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Oct 2017 10:15:18 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v94HFI1t022552; Wed, 4 Oct 2017 10:15:18 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Oct 2017 10:15:18 -0700 From: Steve Kargl To: "Michael W. Lucas" Cc: ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004171518.GA22519@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 17:15:25 -0000 On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > > Poudriere really needs its own small book. Yes, you can do simple > poudriere installs, but once you start covering it properly the docs > quickly expand. My notes alone are longer than my af3e chapter > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > 2018). Please include a discussion on how to use poudriere on a system with limited resouces (e.g., 10 GB of free diskspace and less than 1 GB free memory). I know portmaster works well [1] within an environment with only 4 GB free diskspace and 1 GB memory. [1] portmaster worked well prior to portmgr's decision to displace simple small tools in favor of a sledge hammer. -- Steve From owner-freebsd-ports@freebsd.org Wed Oct 4 17:21:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 807F6E3E7D6 for ; Wed, 4 Oct 2017 17:21:28 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A8E76A93F for ; Wed, 4 Oct 2017 17:21:28 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 59E59E3E7D5; Wed, 4 Oct 2017 17:21:28 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 598A3E3E7D4 for ; Wed, 4 Oct 2017 17:21:28 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 257776A93E for ; Wed, 4 Oct 2017 17:21:28 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id v9so8491427oif.13 for ; Wed, 04 Oct 2017 10:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FGczdvoQ9QTUlHPSf8pZqjb8JqPqlnDw3fh3CaX0nM8=; b=N+oX4MKg2f2MFSYHPtVUlFVNYwCq4Wz2r5qLex2qUhn/nNe/qNTCS9ui2bkBEVdww3 sVrvGB2sXCLsiVArKt7MWaWJ3CQw58UkSxDfu44ml8t7cOHOmB4mFwkbrPdEyz1o4c7c /N4Q36zSLgLTmQNR2mlXNQJ9NTTQNeQ1Mz1AsmvGeeHwjJ6QyB1E/XdGVH++MMciXTq9 1kLm8ebtQ6NUWYRyGtSqBHZKw14BEbrPubBfPKHbGbrK4nDbp9cabv4uB16zfaYeFon7 LIwPETWWVxU91Jlim9avtnOJLuZaBPa0o6sw0BR6DSETPinV2J8+j6l29/4K2n2HP/VR 7Rhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FGczdvoQ9QTUlHPSf8pZqjb8JqPqlnDw3fh3CaX0nM8=; b=FKSnZo7NmP9Srzxj/hw2Jrk90vuFcrp/YqNot0LYJLJ0Do0ulpUW7dMUc5m09XsCJr tB1kagti4Mthq6ayGDSpYZhlvLQVRVwkwTBbwC1p7mymEFSBuWa8KAIpKJQY7L77pGzC FQnJsC36enYygE1talPNjJS7bB7GAYY/xyrWhnplYYmOtv6/abgsFPEthdA54P2Opd4k WDarSUp/vkyzT20IzFkBNaj0mShD7A1HyVUEOSUixeoceWG+TAwuFf08qIErXeq+nsKQ +iZSGjL5rfr4tSpJXmUseG4k+eJn13LEgXtDcx3LldBFqQgPQRh8t8Bt160g4rhp7cxI r9IA== X-Gm-Message-State: AMCzsaVpdnz21SgQgUtb+cLOVU5EOY+MoOTbfBuB9BRfCIQP3H1Pcnjx bnf7ImgrZG32tODKaFXOhQA70AR8QOJ1yZEQeY4= X-Google-Smtp-Source: AOwi7QA7LGGSxEno12sJXR0Kw42Sn2l5biWfw9y8yD1csdKwrV3PiZ4Dq1boqPQ4t6fCmKDvBKdhka6Z3gnSBPapvEM= X-Received: by 10.157.9.195 with SMTP id 3mr12722964otz.431.1507137687352; Wed, 04 Oct 2017 10:21:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.62.245 with HTTP; Wed, 4 Oct 2017 10:21:26 -0700 (PDT) In-Reply-To: <20171004171518.GA22519@troutmask.apl.washington.edu> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> From: Freddie Cash Date: Wed, 4 Oct 2017 10:21:26 -0700 Message-ID: Subject: Re: portmaster, portupgrade, etc To: Steve Kargl Cc: "Michael W. Lucas" , FreeBSD Ports Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 17:21:28 -0000 On Wed, Oct 4, 2017 at 10:15 AM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > > > > Poudriere really needs its own small book. Yes, you can do simple > > poudriere installs, but once you start covering it properly the docs > > quickly expand. My notes alone are longer than my af3e chapter > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > > 2018). > > Please include a discussion on how to use poudriere on > a system with limited resouces (e.g., 10 GB of free > diskspace and less than 1 GB free memory). I know > portmaster works well [1] within an environment with > only 4 GB free diskspace and 1 GB memory. > =E2=80=8BPretty sure the standard response will be along the lines of:=E2= =80=8B By using pkg to fetch/install binary packages that were built by, and are hosted=E2=80=8B on, a separate box that does nothing but run poudriere to b= uild the package repo using your custom specifications and OPTIONS, obviously. :) Why compile ports directly on a box that is so hardware constrained that it will take multiple hours to do, when a "pkg update; pkg upgrade" takes only a few minutes? =E2=80=8B:) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@freebsd.org Wed Oct 4 17:28:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E748E3E8DC for ; Wed, 4 Oct 2017 17:28:14 +0000 (UTC) (envelope-from katelyn.smith@microiworld.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D5CAD6AD03 for ; Wed, 4 Oct 2017 17:28:13 +0000 (UTC) (envelope-from katelyn.smith@microiworld.com) Received: by mailman.ysv.freebsd.org (Postfix) id D202AE3E8DB; Wed, 4 Oct 2017 17:28:13 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D188AE3E8DA for ; Wed, 4 Oct 2017 17:28:13 +0000 (UTC) (envelope-from katelyn.smith@microiworld.com) Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0090.outbound.protection.outlook.com [104.47.100.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE9286AD00 for ; Wed, 4 Oct 2017 17:28:12 +0000 (UTC) (envelope-from katelyn.smith@microiworld.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT2803219.onmicrosoft.com; s=selector1-microiworld-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AuQOkslXLl9spmYdPrUnOJOkbzSQwl9ugVz/nPnJ5LM=; b=AaNRyRP3x1BxjgEEJlHnCT21MlRfk38s9T0/+QOP9ASlkcYETJTzX+UQCm2ycmkZTPKd2utU0OYkqd2acyaKGct+OW5FwCZa3KloZpLjvzqoLwMGaaF6mUN+dCsgJcVe5+3vBS9fqE6vjrayCgpnVctMXq6c8o+f1L5bRSlno7w= Received: from BM1PR01MB0881.INDPRD01.PROD.OUTLOOK.COM (10.174.211.9) by BM1PR01MB0882.INDPRD01.PROD.OUTLOOK.COM (10.174.211.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Wed, 4 Oct 2017 17:28:09 +0000 Received: from BM1PR01MB0881.INDPRD01.PROD.OUTLOOK.COM ([10.174.211.9]) by BM1PR01MB0881.INDPRD01.PROD.OUTLOOK.COM ([10.174.211.9]) with mapi id 15.20.0077.018; Wed, 4 Oct 2017 17:28:09 +0000 From: Katelyn Smith To: "ports@freebsd.org" Subject: Demand Generation Thread-Topic: Demand Generation Thread-Index: AdM9NDA6iS1MICxjToayG0dG1IQsVg== Date: Wed, 4 Oct 2017 17:16:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=katelyn.smith@microiworld.com; x-originating-ip: [49.207.51.177] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BM1PR01MB0882; 6:RONTC5uEBhjCF5zBurSpDv7+Bxgeo+pHEQNJD/UOt1bQhjAj2jV56KLqclgCWNnTX4BregxWk01eIr4LoNvb+B8JB45APLdnfcQldbxPXze0jxmnWAJfONRG5GuYp+PtsGzWfdnKGbeuBPK67hMQUCTByEAe/okfE+aRvOshtVHaPTes6MlaoJoHHrwedLBObw+l6uj6EYgQks6AEFb/wHMTysbjwlptS6gw3Cswk3xWO4k9xgQgOOAK9ak5KAWL57upqjdxUP+kPUUlYBCUdT//0LEfEe440+y0r3fQf/6THLDJ0hLxRDpaZBezglvs+RMcCgLZhglMqBbNZxoBsw==; 5:kYg2hgJaZzfXAb0ZsODBuGiYGQcrctHtd1bLIzD1k5R3JnkQ6exP6XYcjoIxAusnSvo+I04MLLzyC+5yfHXYCy45HA/T5VH1urjqAju961OHszE9/m2gUOAxjEoXnwSgOgPtivsPCPksoNwlfyZ4Kw==; 24:TrRdtKv+YAq124B9qp4TNui7IN+n5R6KiMR/mJLJJf8HfKDtpwYy2R4jqpEoMQ2eWjCXrOGoukUrLkfZJXeSi7ghcDyJSQOLzUIs4bN2NJs=; 7:x1l0wfg7bQl3lRGD+Ks3vtzkLWQQYfeNJHAs2ZlTes3Aa8w5FMZY5FPV1viFmoK87e8E+HTeU3pHr9mKcpcARuryYpOPQLHLFo5DXIegMVXspYG0yhkGmdOLBi86uPYhvf8FX2BA4Micg8gHnS8aevklOe+pb+Nuykr91arGcElGyRC82qe3lsRkgZFyjrRmikud6NTHgaDuj2jgPkrUtA5Hj8BsZ3+aWW8k4ZKkpWg= x-ms-office365-filtering-correlation-id: 5b3f5324-5072-44b5-e50f-08d50b4d481d x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017082002075)(2017052603199)(201703131423075)(201702281549075)(201702085553020)(201702085551020)(201702085555020)(201702085554020); SRVR:BM1PR01MB0882; x-ms-traffictypediagnostic: BM1PR01MB0882: x-exchange-antispam-report-test: UriScan:(21748063052155); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6041248)(2016111802025)(20161123562025)(20161123558100)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(6043046)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BM1PR01MB0882; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BM1PR01MB0882; x-forefront-prvs: 0450A714CB x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(189002)(199003)(101416001)(5630700001)(54356999)(221733001)(68736007)(33656002)(2501003)(790700001)(74316002)(6916009)(2351001)(189998001)(3846002)(6116002)(7736002)(7696004)(5660300001)(102836003)(8676002)(1730700003)(105586002)(81166006)(3480700004)(81156014)(5640700003)(77096006)(6306002)(6436002)(106356001)(6506006)(8936002)(66066001)(6666003)(97736004)(86362001)(7116003)(54896002)(25786009)(2906002)(3660700001)(316002)(55016002)(9686003)(53936002)(2900100001)(626008)(14454004)(50986999)(3280700002)(478600001)(58974002); DIR:OUT; SFP:1102; SCL:1; SRVR:BM1PR01MB0882; H:BM1PR01MB0881.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: microiworld.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: microiworld.com X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2017 17:16:47.5793 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5f482093-8fab-46ad-b760-39c5294d3054 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BM1PR01MB0882 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 17:28:14 -0000 Hello there, When it comes to B2B marketing, the effectiveness of your campaign is almos= t entirely dependent on the quality of your leads. An unreliable set of lea= ds will undoubtedly result in unreliable and possibly disastrous results. At Microiworld we provide consistent lead generation services for all your = B2B ventures. Our coverage is truly massive with North America, Europe, Asi= a and Australia falling under its aegis. We'll even custom build your list = to make sure that the prospects you contact are genuinely interested in hea= ring your pitch. We can also help you reach the top executives within each organization, giv= ing your campaign a boost like no other. Some of the executives we can get = you in touch with include, * C-Level Executives * V-Level Executives * D-level Executives * Chief Procurement Officers * Marketing Directors * Industry Professionals and Specialists Organically grown leads on the other hand are time-consuming, labor-intensi= ve and will only give you a fraction of the kind of sales you'd expect from= a genuine lead generation service like Microiworld. By constructing an ana= lysis of your business goals and proposed campaign, we can create a list th= at perfectly matches specifications to a particular demographic and geograp= hic area. If you're interested please let me know the geography and job title you are= looking out to target for so that we can provide you with counts, pricing,= sample file and more information in my next email. Awaiting for your response, Regards, Katelyn Smith Marketing Executive To Opt Out, please respond "Leave Out" in the Subject line. From owner-freebsd-ports@freebsd.org Wed Oct 4 18:14:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2C47E3F735 for ; Wed, 4 Oct 2017 18:14:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 947566C4A7 for ; Wed, 4 Oct 2017 18:14:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 93C85E3F734; Wed, 4 Oct 2017 18:14:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9366EE3F733 for ; Wed, 4 Oct 2017 18:14:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 74AB16C4A3 for ; Wed, 4 Oct 2017 18:14:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v94IEDnP060737 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Oct 2017 11:14:13 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v94IEDpJ060736; Wed, 4 Oct 2017 11:14:13 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Oct 2017 11:14:13 -0700 From: Steve Kargl To: Freddie Cash Cc: FreeBSD Ports Mailing List , "Michael W. Lucas" Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004181413.GA51148@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 18:14:14 -0000 On Wed, Oct 04, 2017 at 10:21:26AM -0700, Freddie Cash wrote: > On Wed, Oct 4, 2017 at 10:15 AM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > > > > > > Poudriere really needs its own small book. Yes, you can do simple > > > poudriere installs, but once you start covering it properly the docs > > > quickly expand. My notes alone are longer than my af3e chapter > > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > > > 2018). > > > > Please include a discussion on how to use poudriere on > > a system with limited resouces (e.g., 10 GB of free > > diskspace and less than 1 GB free memory). I know > > portmaster works well [1] within an environment with > > only 4 GB free diskspace and 1 GB memory. > > > > ​Pretty sure the standard response will be along the lines of:​ > > By using pkg to fetch/install binary packages that were built by, and are > hosted​ on, a separate box that does nothing but run poudriere to build the > package repo using your custom specifications and OPTIONS, obviously. :) > > Why compile ports directly on a box that is so hardware constrained that it > will take multiple hours to do, when a "pkg update; pkg upgrade" takes only > a few minutes? > Some users cannot afford a 16-core, 32 GB ram, 2TB diskspace box to simply build ports with custom options. In my particular case, this is my last i686 laptop where all of my libm contributions have been and continue to be tested. -- Steve From owner-freebsd-ports@freebsd.org Wed Oct 4 18:57:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AF4CE40345 for ; Wed, 4 Oct 2017 18:57:46 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 65C616D944 for ; Wed, 4 Oct 2017 18:57:46 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: by mailman.ysv.freebsd.org (Postfix) id 61981E40344; Wed, 4 Oct 2017 18:57:46 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F57DE40343 for ; Wed, 4 Oct 2017 18:57:46 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 200C86D943 for ; Wed, 4 Oct 2017 18:57:45 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id v94IvOQZ014674 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 4 Oct 2017 14:57:30 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: portmaster, portupgrade, etc To: sgk@troutmask.apl.washington.edu, Freddie Cash Cc: FreeBSD Ports Mailing List , "Michael W. Lucas" References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> From: George Mitchell Message-ID: <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> Date: Wed, 4 Oct 2017 14:57:08 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171004181413.GA51148@troutmask.apl.washington.edu> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4mrqWnhsK5ti5QevAw7cmW544o8vhSrVN" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Wed, 04 Oct 2017 14:57:31 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 18:57:46 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4mrqWnhsK5ti5QevAw7cmW544o8vhSrVN Content-Type: multipart/mixed; boundary="sO0AE04JxR9WrUr41qX4QALFCcmkv98IK"; protected-headers="v1" From: George Mitchell To: sgk@troutmask.apl.washington.edu, Freddie Cash Cc: FreeBSD Ports Mailing List , "Michael W. Lucas" Message-ID: <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> Subject: Re: portmaster, portupgrade, etc References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> In-Reply-To: <20171004181413.GA51148@troutmask.apl.washington.edu> --sO0AE04JxR9WrUr41qX4QALFCcmkv98IK Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/04/17 14:14, Steve Kargl wrote: > On Wed, Oct 04, 2017 at 10:21:26AM -0700, Freddie Cash wrote: >> On Wed, Oct 4, 2017 at 10:15 AM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >>> On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: >>>> >>>> Poudriere really needs its own small book. Yes, you can do simple >>>> poudriere installs, but once you start covering it properly the docs= >>>> quickly expand. My notes alone are longer than my af3e chapter >>>> limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" i= n >>>> 2018). >>> >>> Please include a discussion on how to use poudriere on >>> a system with limited resouces [...] >> =E2=80=8BPretty sure the standard response will be along the lines of:= =E2=80=8B [...] > Some users cannot afford a 16-core, 32 GB ram, 2TB diskspace box > to simply build ports with custom options. [...] While I agree with you, allow me to insert a gentle reminder that the OP was asking only about whether to include portmaster in his book. I suggest that he should. -- George --sO0AE04JxR9WrUr41qX4QALFCcmkv98IK-- --4mrqWnhsK5ti5QevAw7cmW544o8vhSrVN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlnVLxQACgkQwRES3m+p 4fnPrQ/8DlnCUh6UFsr9sLGrwhaYKsBX0YNjkDgAwT84kHhtGet2WgFP4VA0r0jt g6LJQp/Kf41zsgvN66g70zpMDUmGoPjHOR/cU5qdHVpXGWoWa9MU350M0Hr3TUH1 1b6tmbn3mNu/6je1tku1WyQfcoXgtoDWFXJFhfPzEGpXJUxokyJwUFn14R7QaZlB Cg4c3e4fIp9AjTWaS6ywnnEMVhDC8pg5F8aVU8MbFSr62DWFUzw2pyIPRLpZMeDo iKHSp2zq4tdbidwu7EkHlzjEi6vtbD4eiYf3nmEgpgQcvLe0ilDRMXy70X/pl35N GutAiHBtQZ+zWWpYnkWKv/lywvopt8OXswy9Sp8hk3plqpFsPnm5oI7w7DSS/h5U H37BNIV6LMDLB60V2+n2YRM/ypMCHrHzSL7gZmeYmz/wQP60dIfakZQg4RyOMYYZ iB3g+q+9QMgEwgMNmnCuSs64TrTju0RayM60wl5BoB/Qu6kw290zwROd3aWEC4zk 9aHPKlMsEdegdveb1JrQM47Ak7uW5YG7GTA4I/t5HCJtVzTqi6aDhZBPNUp2yW88 XvALbf7vJgyFeT+YiXYs7YTTNf7PyEEictRLnA2MyiGLcSwrZZpR9I3bpv3//P4i yE8DI+FDpn9G3vMWJsp5Rju2Sn5dNgoe40D1oNJSPnpfkDyIqck= =ynZ7 -----END PGP SIGNATURE----- --4mrqWnhsK5ti5QevAw7cmW544o8vhSrVN-- From owner-freebsd-ports@freebsd.org Wed Oct 4 19:40:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D2FCE40E34 for ; Wed, 4 Oct 2017 19:40:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 52F4A6E97C for ; Wed, 4 Oct 2017 19:40:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 4F349E40E33; Wed, 4 Oct 2017 19:40:27 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EC03E40E32 for ; Wed, 4 Oct 2017 19:40:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 16BE06E97B for ; Wed, 4 Oct 2017 19:40:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v94JeQCi010883 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Oct 2017 12:40:26 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v94JePR6010882; Wed, 4 Oct 2017 12:40:25 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Oct 2017 12:40:25 -0700 From: Steve Kargl To: George Mitchell Cc: Freddie Cash , FreeBSD Ports Mailing List , "Michael W. Lucas" Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004194025.GA10412@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 19:40:27 -0000 On Wed, Oct 04, 2017 at 02:57:08PM -0400, George Mitchell wrote: > On 10/04/17 14:14, Steve Kargl wrote: > > On Wed, Oct 04, 2017 at 10:21:26AM -0700, Freddie Cash wrote: > >> On Wed, Oct 4, 2017 at 10:15 AM, Steve Kargl < > >> sgk@troutmask.apl.washington.edu> wrote: > >> > >>> On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > >>>> > >>>> Poudriere really needs its own small book. Yes, you can do simple > >>>> poudriere installs, but once you start covering it properly the docs > >>>> quickly expand. My notes alone are longer than my af3e chapter > >>>> limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > >>>> 2018). > >>> > >>> Please include a discussion on how to use poudriere on > >>> a system with limited resouces [...] > >> ​Pretty sure the standard response will be along the lines of:​ [...] > > Some users cannot afford a 16-core, 32 GB ram, 2TB diskspace box > > to simply build ports with custom options. [...] > While I agree with you, allow me to insert a gentle reminder that the > OP was asking only about whether to include portmaster in his book. > I suggest that he should. -- George Ahem, yeah, so I'm not allowed to request a short description on how to use poudiere in a resource constrained environment? -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Wed Oct 4 20:25:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07814E41B50 for ; Wed, 4 Oct 2017 20:25:51 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B50B70192 for ; Wed, 4 Oct 2017 20:25:49 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x527162a6.dyn.telefonica.de [82.113.98.166]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v94KDLSZ035828 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Oct 2017 20:13:22 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x527162a6.dyn.telefonica.de [82.113.98.166] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> From: Grzegorz Junka Message-ID: Date: Wed, 4 Oct 2017 20:13:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:25:51 -0000 On 04/10/2017 16:16, Michael W. Lucas wrote: > Hi, > > I'm doing tech edits on the new edition of "Absolute FreeBSD," and > stumbled into what's apparently a delicate topic. > > Some of my reviewers are happy I included portmaster in the book. > > Some reviewers beg me not to include it. > > Unfortunately, people will be reading af3e and considering it > definitive for the next several years. So I have to get a feel for > where things are going. :-/ > > I've read a couple threads on portmaster's current problems/growing > pains and its looming difficulty with forthcoming flavors. > > I've been a happy portmaster user for many years now. All things being > equal, if its future is still being debated I'm inclined to keep it in > the book. > > Poudriere really needs its own small book. Yes, you can do simple > poudriere installs, but once you start covering it properly the docs > quickly expand. My notes alone are longer than my af3e chapter > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > 2018). > > Truly, I'm not looking to start a flame war here. I only want a bit of > guidance on The Future... > If describing the basic usage of poudriere takes more than 2-3 pages then something is wrong. The handbook has it covered in just a few paragraphs: https://www.freebsd.org/doc/handbook/ports-poudriere.html When I moved to FreeBSD I tried for months to use portmaster and portupgrade because that was the official way described in the handbook. But there were always problems. I was happy when my system was still usable after an upgrade, not mentioning the upgraded ports to work as expected. I remember often thinking, what kind of system this FeeBSD is if even a simple update from sources can screw up so many things! Is anyone really using it, or is it some kind of niche OS, the sort of MorphOS or AROS? I started looking on the internet how others compile it, and I discovered that I was doing it all wrong!!! I read that handbook chapter and it all made sense. I was trying to compile with the system that was being updated at the same time - this can't possibly work (or can it?). I spent one afternoon setting up poudriere and I haven't looked back since then. If you wish please mention portmaster and/or portupgrade, but IN ADDITION to poudriere. I can't imagine a serious book on FreeBSD not giving at least as much space to poudriere as to the other tools. It's great that Absolute FreeBSD is getting an update. That was an indispensable source of information when I was learning the FreeBSD way. But it became outdated quite quickly. Please make an effort to discuss things that are not getting outdated as quickly this time. GrzegorzJ From owner-freebsd-ports@freebsd.org Wed Oct 4 20:30:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61082E41D86 for ; Wed, 4 Oct 2017 20:30:59 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E5FCB70502 for ; Wed, 4 Oct 2017 20:30:58 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x527162a6.dyn.telefonica.de [82.113.98.166]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v94KUtNq036056 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Oct 2017 20:30:56 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x527162a6.dyn.telefonica.de [82.113.98.166] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> From: Grzegorz Junka Message-ID: Date: Wed, 4 Oct 2017 20:30:49 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171004194025.GA10412@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:30:59 -0000 On 04/10/2017 19:40, Steve Kargl wrote: > On Wed, Oct 04, 2017 at 02:57:08PM -0400, George Mitchell wrote: >> On 10/04/17 14:14, Steve Kargl wrote: >>> On Wed, Oct 04, 2017 at 10:21:26AM -0700, Freddie Cash wrote: >>>> On Wed, Oct 4, 2017 at 10:15 AM, Steve Kargl < >>>> sgk@troutmask.apl.washington.edu> wrote: >>>> >>>>> On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: >>>>>> Poudriere really needs its own small book. Yes, you can do simple >>>>>> poudriere installs, but once you start covering it properly the docs >>>>>> quickly expand. My notes alone are longer than my af3e chapter >>>>>> limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in >>>>>> 2018). >>>>> Please include a discussion on how to use poudriere on >>>>> a system with limited resouces [...] >>>> ​Pretty sure the standard response will be along the lines of:​ [...] >>> Some users cannot afford a 16-core, 32 GB ram, 2TB diskspace box >>> to simply build ports with custom options. [...] >> While I agree with you, allow me to insert a gentle reminder that the >> OP was asking only about whether to include portmaster in his book. >> I suggest that he should. -- George > Ahem, yeah, so I'm not allowed to request a short description > on how to use poudiere in a resource constrained environment? > The environment isn't constrained by poudriere but by the ports you want to compile. When compiling libreoffice or chromium or firefox I don't think there is anything else that can be done than setting poudriere to run no more than 1 job at a time. Poudriere itself doesn't take any additional resources, it's just a dedicated jail and a bunch of scripts. I would rather say that the amount of resources poudriere takes to compile stuff is normal, the baseline. Portmaster or portupgrade make a compromise - unstable compilation environment for some additional memory to compile especially resource hungry ports. What I am trying to say is that there isn't probably much to discuss. However, explaining the difference between portmaster/portupgrade and poudriere and how to plan computer resources for compiling various sizes of ports may be more useful? GrzegorzJ From owner-freebsd-ports@freebsd.org Wed Oct 4 20:39:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E2A6E422B4 for ; Wed, 4 Oct 2017 20:39:29 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 38ED270E67 for ; Wed, 4 Oct 2017 20:39:29 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3459AE422B3; Wed, 4 Oct 2017 20:39:29 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33D9DE422B2 for ; Wed, 4 Oct 2017 20:39:29 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFCB270E66 for ; Wed, 4 Oct 2017 20:39:28 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-qt0-x234.google.com with SMTP id 6so12608230qtw.3 for ; Wed, 04 Oct 2017 13:39:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=iTZWghUwFw9Znsr1xcrtr0cneUtL/7M4fjvlc8tdSew=; b=ba0VFJ7DMvKdWAJod4GH4XksmF4hG5+SHnGzTynTUFpySRZKIT5NaNpFPdwIIqD6M1 KdOvs5yhcumJc39Fz8RfweqpObMmOMPeesoWm/6yunxJ6z/oUwOVtJFL+qWT0KSYrRan EAeorcMFiXNTfImk5vaxnn56KrsbR+Jzv9ICUNK2Ju9cQNVBAcgikg3HspukbFjJtehj K+jT1/z+bvNrbnNS2zfQjd+rz8Puwb1zxfxDmrYVvkyD3Qz3kL28+HLic5IXSgQkn282 d6Vvrq47VdnKTWac95SxnqXRI3tSpDQF3UUY3RtDZ4GQgkWdrXPNBhWQRj0QsjN9n5uG N6Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=iTZWghUwFw9Znsr1xcrtr0cneUtL/7M4fjvlc8tdSew=; b=ZX8R8x/WsXGZyFW0T/B5rwmrlTfq6t59CLN2fCG4lRh5MCzWRx1NjdO8/km+eXKnJl skNCP6jO44Bv5wnDdrD7BGjHavDYU65fdKg+ZFCvRVo9PEebA3ZrKKbQ+qL/QvAJeMMv EX7CBPK+AHE3DwU5ZD2Rz0lu0rmINUklixzMBGyBAtNFZTZg6aRy/u3Qvd+HQHrStS5h lSGsXs5I4JTaf/rLpJVGPuXwR5ERug3ZjQe/KoYFKoYd492tDpPQhjCQ2lMP0K5Ugju1 MdcaL5RuDNeqWTRDsimEZg0mPXBpA1/sb+U7xWylK9+YenaIgLtvR0Bhgm+ZxledgMbB 4Bkg== X-Gm-Message-State: AMCzsaU5hLWTz0OOHkiQePJDNb6upr4JxSH2eYM8Z1/RKlhmgehuriyp /O33vkqGa0mJXCzkDuhATY+/mQ== X-Google-Smtp-Source: AOwi7QBDNiu9KDO0RRP7Vkf5R3J1zykMQqtCLAjgnczZ3LJeHYbU/EeZaiPTH0/CBEXw5Nex6zih5g== X-Received: by 10.237.63.15 with SMTP id p15mr28735755qtf.113.1507149567994; Wed, 04 Oct 2017 13:39:27 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-147.neo.res.rr.com. [74.141.88.147]) by smtp.googlemail.com with ESMTPSA id n29sm10902395qta.61.2017.10.04.13.39.27 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 04 Oct 2017 13:39:27 -0700 (PDT) Message-ID: <59D546FD.30906@gmail.com> Date: Wed, 04 Oct 2017 16:39:25 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "Michael W. Lucas" CC: ports@freebsd.org Subject: Re: portmaster, portupgrade, etc References: <20171004161649.GA51883@mail.michaelwlucas.com> In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:39:29 -0000 Michael W. Lucas wrote: > Hi, > > I'm doing tech edits on the new edition of "Absolute FreeBSD," and > stumbled into what's apparently a delicate topic. > > Some of my reviewers are happy I included portmaster in the book. > > Some reviewers beg me not to include it. > > Unfortunately, people will be reading af3e and considering it > definitive for the next several years. So I have to get a feel for > where things are going. :-/ > > I've read a couple threads on portmaster's current problems/growing > pains and its looming difficulty with forthcoming flavors. > > I've been a happy portmaster user for many years now. All things being > equal, if its future is still being debated I'm inclined to keep it in > the book. > > Poudriere really needs its own small book. Yes, you can do simple > poudriere installs, but once you start covering it properly the docs > quickly expand. My notes alone are longer than my af3e chapter > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > 2018). > > Truly, I'm not looking to start a flame war here. I only want a bit of > guidance on The Future... > > ==ml > Here's my take on that. The future direction has already been decided by the FreeBSD leaders 2 years ago with their development of a better pkg system. The package system with flavors will cover 90% of the user community needs. The remaining user's requirements are edge cases. Tools like portmaster and portupgrad and even the native ports system usage on personal machines will fad away. The ports system will mature into the development system in the path to get things into the package system. You adding details on these port system tools will only give the reader the impression that they are still popular and being actively supported thus working against the intended direction Freebsd package system is headed. Making it even harder to get users to move forward. Don't let the few old school die hearts who are afraid of any change and make the most noise influence you. There will always be edge case user who think their needs out weight what is best for the group. Remember that your updated book will become a bible for many years and many readers. Don't include items that are now on the edge of being replaced. Another candidate is JAILs IE: the old way of jail definition was in rc.conf the new way being jail.conf. The jail.conf method was introduction was at RELEASE 9.0 and here its 11.1 and still the old school users fight to retain both ways. Hoping that with 12.0, support for jail definition in rc.conf will be totally removed. One last though. The problem with the Freebsd handbook is that it reads like a list of reminder notes. The reader is expected to already have a well defined understanding of the subject being read about. The past 2 years a great amount of effort has gone into bring the handbook up to date with the current status of the operating system. But it is a very far cry from a teaching aid. Please take the time to rework the original "Absolute FreeBSD" content into something that is usable as a teaching book. You must assume that the only thing the reader knows about Freebsd is how to spell the word Freebsd and build the content from there. Good luck. From owner-freebsd-ports@freebsd.org Wed Oct 4 20:43:22 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95435E42529 for ; Wed, 4 Oct 2017 20:43:22 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DCF471509 for ; Wed, 4 Oct 2017 20:43:21 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 276AABCF; Wed, 4 Oct 2017 15:43:15 -0500 (CDT) Date: Wed, 4 Oct 2017 15:43:14 -0500 From: Mark Linimon To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004204313.GA7679@lonesome.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:43:22 -0000 On Wed, Oct 04, 2017 at 08:13:16PM +0000, Grzegorz Junka wrote: > I was trying > to compile with the system that was being updated at the > same time - this can't possibly work (or can it?). It works somewhere between "quite often" to "nearly all the time". It can vary depending on the complexity of the ports you have installed, what state the tree is in, how much the ports you use are often used by others, and subtle differences in changes to port dependencies. This is complex enough to be indistinguishable from "phase of the moon." In this case I really wish I were joking. mcl From owner-freebsd-ports@freebsd.org Wed Oct 4 20:56:10 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77A4DE427BB for ; Wed, 4 Oct 2017 20:56:10 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DBE4B71B4B for ; Wed, 4 Oct 2017 20:56:09 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v94Ku7cm036503 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Oct 2017 20:56:07 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004204313.GA7679@lonesome.com> From: Grzegorz Junka Message-ID: Date: Wed, 4 Oct 2017 20:56:00 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171004204313.GA7679@lonesome.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:56:10 -0000 On 04/10/2017 20:43, Mark Linimon wrote: > On Wed, Oct 04, 2017 at 08:13:16PM +0000, Grzegorz Junka wrote: >> I was trying >> to compile with the system that was being updated at the >> same time - this can't possibly work (or can it?). > It works somewhere between "quite often" to "nearly all > the time". It can vary depending on the complexity of Well, that's not my experience. For me it worked occasionally at best. A few times the system became so broken that many applications couldn't be opened any more and I had to spend hours to restore it to some kind of usability. Even with poudriere I still manage to break the ports quite often by setting various options not to their recommended values - see defects I have been raising on https://www.freebsd.org/support/bugreports.html But at least I am not able to install them until they are fixed. Maybe I am just too ambitious or maybe poudriere is more idiot-proof? I guess portmaster or portupgrade may work fine if one uses the default options, but in that case, hey, why bother? Just use the compiled packages! If you try to change some ports to non-default options, and something doesn't compile, portmaster/portupgrade will leave the system in half-baked state. And then only heavens can help... > the ports you have installed, what state the tree is in, > how much the ports you use are often used by others, and > subtle differences in changes to port dependencies. > > This is complex enough to be indistinguishable from "phase > of the moon." > > In this case I really wish I were joking. > > mcl > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Wed Oct 4 20:57:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E3FEE42826 for ; Wed, 4 Oct 2017 20:57:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8B6A771BFE for ; Wed, 4 Oct 2017 20:57:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8ABEFE42825; Wed, 4 Oct 2017 20:57:07 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A5C2E42824 for ; Wed, 4 Oct 2017 20:57:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67C7771BFD for ; Wed, 4 Oct 2017 20:57:06 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 91A74BCF; Wed, 4 Oct 2017 15:57:05 -0500 (CDT) Date: Wed, 4 Oct 2017 15:57:04 -0500 From: Mark Linimon To: Ernie Luzar Cc: "Michael W. Lucas" , ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004205704.GB7679@lonesome.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59D546FD.30906@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 20:57:07 -0000 On Wed, Oct 04, 2017 at 04:39:25PM -0400, Ernie Luzar wrote: > even the native ports system usage on personal machines > wwill fade away. I have seen this claim many times by users but AFAIR that was never a goal. The feeling was that _most_ users would migrate to using packages, once using packages had been made much easier and more robust than the previous packaging technology. (Disclaimer: I was much more familiar with the internals of the old pkg-* tools and the bad state that they had gotten into.) > The past 2 years a great > amount of effort has gone into bring the handbook up to > date with the current status of the operating system. But > it is a very far cry from a teaching aid. I have some proposed patches for the ports section that need to be dusted off and committed. But I think your critism is valid -- it works as a reference better than as a tutorial. The latter is not fixable in the near-term (simply due to volunteer cycles). mcl From owner-freebsd-ports@freebsd.org Wed Oct 4 21:00:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3227FE428F2 for ; Wed, 4 Oct 2017 21:00:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 070E671CF3 for ; Wed, 4 Oct 2017 21:00:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 8FF3FC51; Wed, 4 Oct 2017 16:00:05 -0500 (CDT) Date: Wed, 4 Oct 2017 16:00:04 -0500 From: Mark Linimon To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004210004.GC7679@lonesome.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004204313.GA7679@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 21:00:07 -0000 On Wed, Oct 04, 2017 at 08:56:00PM +0000, Grzegorz Junka wrote: > Maybe I am just too ambitious or maybe poudriere is more > idiot-proof? My possibly incorrect understanding is that poudriere trades off doing a lot more work in an attempt to produce more rigorously correct results. mcl From owner-freebsd-ports@freebsd.org Wed Oct 4 21:11:08 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 983BDE42E05 for ; Wed, 4 Oct 2017 21:11:08 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55443725EA for ; Wed, 4 Oct 2017 21:11:08 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-oi0-x233.google.com with SMTP id f3so21708450oia.2 for ; Wed, 04 Oct 2017 14:11:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SdzH8l41dsvMAUmeuWMOqFIFZ3NqG6rG6Y/sXEU+uLM=; b=fNJ3nKwEo70LhZRyw/6xwahsYiPCbN4b+2IRA/UYKNWKg/MtXl/UrHs7UPu+CS1fDO D62G46RPajGKsqTeSPudfxe8rbqYjJDzp/goj4Wg+n0HE4khkxntI52UwfW8bCPDDr1M ez4MoSP2criYHEGcbmFiqPzxSDyjkmPJZhvmZ5jSBJTnviikFEWv1xjB9qVeLwOBIMFW fammNDZ9wK1U+ICzQPvIlfnNG8Pb1HWPndFCUehnv0V2/B1JKyK3dqyQC/PqTYKJn2zX hPiCHG0fgJbvJjZaU408sPQHhYRdgkcI5MZcsaJ/TDQm3KsFKdPpC3j10KENgHm2oO7Y GJgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SdzH8l41dsvMAUmeuWMOqFIFZ3NqG6rG6Y/sXEU+uLM=; b=WtWb5v0PNk1YpkoIhasQfiPL5DvXL4G64ZyCs48H4lZ3lRmb8o6DxkqtA+kKfkMAeG uVF4DFo02t2JzKYPsEsCHyyE5aonuqKiz6zRBmQhJd6MATzyGHAo3bJYo9iT4bjeePO1 0qqAzoNSdo2Pf387AJP4gx6I+lkgGDV8L5S0DleploIKg8tmZGPxKXxpTWi0h+E/oUil KN+CULcu5CXIQNQjBsG0WjMfO5xpfM5DTL0APfg5wYnn/rGKtVOIpq6liaZe8FqVpiWl t1JhYubCIy73mqxY/mEAQ63WCQqNAk1qsTuKUGRokSVdHlKazfeYRMT26ZlPnB2mgFmk w6fw== X-Gm-Message-State: AMCzsaWd6/F+Ee5vIsBNg62yI86mlHFwc28cdWv1OKC5mdbF+vDjP/uS qim8Y3UOiLhMicYyCfmE4rAZfsdNyNTlmNuHU/4= X-Google-Smtp-Source: AOwi7QA8ZMKNpoq9deuUonAWiE6Thf3rZrlDXAmI6AsfLq/hPAcf0f8tI/FdMTpSHnq22WiHqQC7Ur0OupOFAzLSTIQ= X-Received: by 10.157.85.80 with SMTP id h16mr3974931oti.12.1507151467577; Wed, 04 Oct 2017 14:11:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.62.245 with HTTP; Wed, 4 Oct 2017 14:11:06 -0700 (PDT) In-Reply-To: References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004204313.GA7679@lonesome.com> From: Freddie Cash Date: Wed, 4 Oct 2017 14:11:06 -0700 Message-ID: Subject: Re: portmaster, portupgrade, etc To: Grzegorz Junka Cc: freebsd-ports Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 21:11:08 -0000 On Wed, Oct 4, 2017 at 1:56 PM, Grzegorz Junka wrote: > > On 04/10/2017 20:43, Mark Linimon wrote: > >> On Wed, Oct 04, 2017 at 08:13:16PM +0000, Grzegorz Junka wrote: >> >>> I was trying >>> to compile with the system that was being updated at the >>> same time - this can't possibly work (or can it?). >>> >> It works somewhere between "quite often" to "nearly all >> the time". It can vary depending on the complexity of >> > > Well, that's not my experience. For me it worked occasionally at best. A > few times the system became so broken that many applications couldn't be > opened any more and I had to spend hours to restore it to some kind of > usability. Even with poudriere I still manage to break the ports quite > often by setting various options not to their recommended values - see > defects I have been raising on https://www.freebsd.org/suppor > t/bugreports.html But at least I am not able to install them until they > are fixed. > > Maybe I am just too ambitious or maybe poudriere is more idiot-proof? I > guess portmaster or portupgrade may work fine if one uses the default > options, but in that case, hey, why bother? Just use the compiled package= s! > If you try to change some ports to non-default options, and something > doesn't compile, portmaster/portupgrade will leave the system in half-bak= ed > state. And then only heavens can help... =E2=80=8BThe nice thing about poudriere is that it doesn't affect the runni= ng system. The act of creating the package repo is completely separate from the act of installing packages. The two steps can be done on a single system, or on separate systems. During the creation of the package repo via poudriere, nothing on the client system is affected; nothing is installed, nothing is uninstalled. One can continue to use the system, which is great for desktops and critical servers alike. If there's an issue compiling a port in the middle of a long dependency chain in poudriere, the process stops and you work to fix it. Nothing you do at this point affects any of the client(s). If you can't get it fixed, you don't have to worry about rolling back versions on the client(s) to get things back to a working state. Only once you have everything compiled and packaged up do you worry about the client system(s). And there, the pkg system takes over and handles everything. It's pretty much a "everything works or nothing gets installed" process at that time (with very few corner cases that break things). It's not bulletproof, but it's a lot safer than compiling things on the live system where some compiler bits are picked up from the ports build tree, while other bits are picked up from the live filesystem, while some things are auto-detected based on other installed ports, while some things are skipped for the same reason, etc. Will there be situations where you want to compile directly on the client? Maybe. Will there be many people that need that against all other options? Not really. the ports you have installed, what state the tree is in, >> how much the ports you use are often used by others, and >> subtle differences in changes to port dependencies. >> >> This is complex enough to be indistinguishable from "phase >> of the moon." >> >> In this case I really wish I were joking. >> > =E2=80=8BI used to love compiling everything on my home systems and work sy= stems. Then KDE upgrades kept leaving me with a broken system due to enabling some esoteric OPTIONS that I thought I needed and portmaster would fail in the middle of the umpteen-level-deep dependency chain. I could usually get things back to a working, upgraded state, but that usually left me without a working GUI for 2-4 days. The introduction of pkg has alleviated me of= =E2=80=8B that need. :) I don't even have /usr/ports installed on my home or work systems anymore. After ending up with a broken server at work for the same reason I switched those to using pkg only. I played with poudriere back in the early days and it was easy to work with. But I found myself setting fewer and fewer custom OPTIONS so the need for it diminished with time. Debated playing with it at work to get a custom OpenSSH package (for NONE encryption), but I found other ways to do the same. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@freebsd.org Wed Oct 4 21:22:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A881E43145 for ; Wed, 4 Oct 2017 21:22:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D47472D16 for ; Wed, 4 Oct 2017 21:22:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v94LMQXg027544 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Oct 2017 14:22:26 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v94LMPGK027543; Wed, 4 Oct 2017 14:22:25 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Oct 2017 14:22:25 -0700 From: Steve Kargl To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004212225.GA26638@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 21:22:27 -0000 On Wed, Oct 04, 2017 at 08:30:49PM +0000, Grzegorz Junka wrote: > > On 04/10/2017 19:40, Steve Kargl wrote: > > Ahem, yeah, so I'm not allowed to request a short description > > on how to use poudiere in a resource constrained environment? > > > > The environment isn't constrained by poudriere but by the ports you want > to compile. When compiling libreoffice or chromium or firefox I don't > think there is anything else that can be done than setting poudriere to > run no more than 1 job at a time. Poudriere itself doesn't take any > additional resources, it's just a dedicated jail and a bunch of scripts. > I did not state that the "environment is constrained by poudriere". The environment is contrained due to resource limits. If you only have 1 Gb of memory and 5-10 GB diskspace, then using poudriere with zfs and jails is a nonstarter. Yes, I'm aware that zfs is not required. Can't find info on whether jails can be avoided. Having say lang/llvm40 installed in /usr/local and in a jail would consumes 2.6 GB. That's 1 port! -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Wed Oct 4 21:46:09 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F019E43839 for ; Wed, 4 Oct 2017 21:46:09 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6517A735C0 for ; Wed, 4 Oct 2017 21:46:07 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v94Lk5Hj037334 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Oct 2017 21:46:05 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> <20171004212225.GA26638@troutmask.apl.washington.edu> From: Grzegorz Junka Message-ID: <8bd938c0-6c08-6182-5e75-0441a4b5e6ec@gjunka.com> Date: Wed, 4 Oct 2017 21:46:00 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171004212225.GA26638@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 21:46:09 -0000 On 04/10/2017 21:22, Steve Kargl wrote: > On Wed, Oct 04, 2017 at 08:30:49PM +0000, Grzegorz Junka wrote: >> On 04/10/2017 19:40, Steve Kargl wrote: >>> Ahem, yeah, so I'm not allowed to request a short description >>> on how to use poudiere in a resource constrained environment? >>> >> The environment isn't constrained by poudriere but by the ports you want >> to compile. When compiling libreoffice or chromium or firefox I don't >> think there is anything else that can be done than setting poudriere to >> run no more than 1 job at a time. Poudriere itself doesn't take any >> additional resources, it's just a dedicated jail and a bunch of scripts. >> > I did not state that the "environment is constrained by poudriere". > The environment is contrained due to resource limits. If you > only have 1 Gb of memory and 5-10 GB diskspace, then using poudriere > with zfs and jails is a nonstarter. Yes, I'm aware that zfs is not > required. Can't find info on whether jails can be avoided. Having > say lang/llvm40 installed in /usr/local and in a jail would consumes > 2.6 GB. That's 1 port! > Would temporarily spinning up an EC2 instance on AWS be an option? It's priced per hour so shouldn't cost much to compile required packages? On the other hand, a desktop with 4GB of RAM and 250GB HDD costs $50-100. I sometimes think if setting up a build system where someone would be able to build ports with their own customized options could become popular... GrzegorzJ From owner-freebsd-ports@freebsd.org Wed Oct 4 21:57:01 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFC35E43C12 for ; Wed, 4 Oct 2017 21:57:01 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 758FB73BAE for ; Wed, 4 Oct 2017 21:57:00 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v94LuwTc037546 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Oct 2017 21:56:59 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004204313.GA7679@lonesome.com> <20171004210004.GC7679@lonesome.com> From: Grzegorz Junka Message-ID: <54f0686e-5619-ed29-cf39-08eef43c6225@gjunka.com> Date: Wed, 4 Oct 2017 21:56:53 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171004210004.GC7679@lonesome.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 21:57:01 -0000 On 04/10/2017 21:00, Mark Linimon wrote: > On Wed, Oct 04, 2017 at 08:56:00PM +0000, Grzegorz Junka wrote: >> Maybe I am just too ambitious or maybe poudriere is more >> idiot-proof? > My possibly incorrect understanding is that poudriere > trades off doing a lot more work in an attempt to produce > more rigorously correct results. > I think it's the other way around. Poudriere does as much as a standalone build server would have to do, but it does it in a jail, so the main system isn't affected and can be used to non-build related work in the meantime. It's portmaster/portupgrade that trade off doing less work with less resources in an attempt to produce less rigorously correct result (and often no result at all, or even an additional work needed to restore the build server to a working condition). From owner-freebsd-ports@freebsd.org Wed Oct 4 22:29:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7E1EE0D2A0 for ; Wed, 4 Oct 2017 22:29:17 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BBE1E746A9 for ; Wed, 4 Oct 2017 22:29:17 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 9E591BCF; Wed, 4 Oct 2017 17:29:15 -0500 (CDT) Date: Wed, 4 Oct 2017 17:29:14 -0500 From: Mark Linimon To: Steve Kargl Cc: Grzegorz Junka , freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004222914.GA7908@lonesome.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> <20171004212225.GA26638@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171004212225.GA26638@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 22:29:18 -0000 Please understand that I'm not trying to be obstinate, I'm trying to understand. Background: years ago I managed the cluster of i386 blades that we used in package building. 933MHz and 512MB IIRC. So I am familiar with constraint problems. On Wed, Oct 04, 2017 at 02:22:25PM -0700, Steve Kargl wrote: > Can't find info on whether jails can be avoided. I have not checked the code but IIRC, no. I thought jails had low memory overhead, though. > If you only have 1 Gb of memory and 5-10 GB diskspace, > then using poudriere with zfs and jails is a nonstarter. For point of comparison, with those constraints, I do not understand how modern llvms can build at all. What happens if you use the manual approach on this same system? e.g. cd /usr/ports/devel/llvm40 mkdir -p /usr/ports/packages make && make package pkg install /usr/ports/packages/llvm.txz Do you still run out of resources? In that case, there's not much that can be done. The compilers, the office suites, and certain math packages are huge beasts. However you try to build them won't matter. I would think having a copy of the llvm workfiles in a jail is going to be equivalent to having them in /tmp? I must be missing something. mcl From owner-freebsd-ports@freebsd.org Wed Oct 4 22:31:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E13A3E0D358 for ; Wed, 4 Oct 2017 22:31:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C725D7494B for ; Wed, 4 Oct 2017 22:31:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 9A4F4BCF; Wed, 4 Oct 2017 17:31:27 -0500 (CDT) Date: Wed, 4 Oct 2017 17:31:26 -0500 From: Mark Linimon To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004223126.GB7908@lonesome.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004204313.GA7679@lonesome.com> <20171004210004.GC7679@lonesome.com> <54f0686e-5619-ed29-cf39-08eef43c6225@gjunka.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54f0686e-5619-ed29-cf39-08eef43c6225@gjunka.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 22:31:29 -0000 On Wed, Oct 04, 2017 at 09:56:53PM +0000, Grzegorz Junka wrote: > portmaster/portupgrade trade off doing less work with > less resources in an attempt to produce less rigorously > correct result That was what I thought I said :-) or at least was trying to say. mcl From owner-freebsd-ports@freebsd.org Wed Oct 4 23:28:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FDD4E237F3 for ; Wed, 4 Oct 2017 23:28:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BAD97666D for ; Wed, 4 Oct 2017 23:28:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v94NSKZc086245 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Oct 2017 16:28:20 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v94NSJWs086244; Wed, 4 Oct 2017 16:28:19 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Oct 2017 16:28:19 -0700 From: Steve Kargl To: Mark Linimon Cc: Grzegorz Junka , freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171004232819.GA86102@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> <20171004212225.GA26638@troutmask.apl.washington.edu> <20171004222914.GA7908@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171004222914.GA7908@lonesome.com> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 23:28:21 -0000 On Wed, Oct 04, 2017 at 05:29:14PM -0500, Mark Linimon wrote: > Please understand that I'm not trying to be obstinate, > I'm trying to understand. Me too. > Background: years ago I managed the cluster of i386 blades > that we used in package building. 933MHz and 512MB IIRC. > So I am familiar with constraint problems. The system in question is my last i686 laptop, which I use for libm development and testing. Once I cannot use that laptop (whether hardware failure or inability to update the installed ports), I'll stop worrying about a functional libm on 32-bit hardware. > On Wed, Oct 04, 2017 at 02:22:25PM -0700, Steve Kargl wrote: > > Can't find info on whether jails can be avoided. > > I have not checked the code but IIRC, no. I thought jails > had low memory overhead, though. That's good, but memory overhead isn't the problem with a jail. It's the diskspace used to duplicate everything already available in /bin:/usr/bin:/usr/local/bin:... and storage to hold the packages as things get built. > > If you only have 1 Gb of memory and 5-10 GB diskspace, > > then using poudriere with zfs and jails is a nonstarter. > > For point of comparison, with those constraints, I do not > understand how modern llvms can build at all. > > What happens if you use the manual approach on this same > system? e.g. > > cd /usr/ports/devel/llvm40 > mkdir -p /usr/ports/packages > make && make package > pkg install /usr/ports/packages/llvm.txz I normally do portmaster -Byd devel/llvm40 and wait a day for the build to complete. I have /usr/ports/distfiles symlinked to a USB2 /mnt/distfiles (40 MB/s max throughput). I may also need to set DISABLE_MAKE_JOBS="YES", but can't remember offhand. > > Do you still run out of resources? > No. I have 4 GB of swap space, which is well used during the build. The system is actually quite usable as portmaster runs. I also build libreoffice and octave on the system. > In that case, there's not much that can be done. The > compilers, the office suites, and certain math packages > are huge beasts. However you try to build them won't > matter. > > I would think having a copy of the llvm workfiles in a jail > is going to be equivalent to having them in /tmp? > > I must be missing something. portmaster satisfies its dependencies from already installed ports in /usr/local. There isn't a clean room full of pkg'd dependencies sitting in some jail while llvm40 builds. So, I think the issue comes down to "portmaster allows an in-place update of installed ports" vs "poudriere builds a repository of packages from which one can then do an update" -- Steve From owner-freebsd-ports@freebsd.org Thu Oct 5 00:27:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9013E24EF0 for ; Thu, 5 Oct 2017 00:27:21 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A1B9D77E16 for ; Thu, 5 Oct 2017 00:27:21 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v950RBFT047711; Wed, 4 Oct 2017 17:27:15 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201710050027.v950RBFT047711@gw.catspoiler.org> Date: Wed, 4 Oct 2017 17:27:11 -0700 (PDT) From: Don Lewis Subject: Re: portmaster, portupgrade, etc To: sgk@troutmask.apl.washington.edu cc: linimon@lonesome.com, list1@gjunka.com, freebsd-ports@freebsd.org In-Reply-To: <20171004232819.GA86102@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 00:27:21 -0000 On 4 Oct, Steve Kargl wrote: > On Wed, Oct 04, 2017 at 05:29:14PM -0500, Mark Linimon wrote: >> Please understand that I'm not trying to be obstinate, >> I'm trying to understand. > > Me too. > >> Background: years ago I managed the cluster of i386 blades >> that we used in package building. 933MHz and 512MB IIRC. >> So I am familiar with constraint problems. > > The system in question is my last i686 laptop, which I > use for libm development and testing. Once I cannot use > that laptop (whether hardware failure or inability to > update the installed ports), I'll stop worrying about a > functional libm on 32-bit hardware. As an aside, this sort of thing could be done in an i386 VM or maybe an i386 jail on amd64 hardware. >> On Wed, Oct 04, 2017 at 02:22:25PM -0700, Steve Kargl wrote: >> > Can't find info on whether jails can be avoided. >> >> I have not checked the code but IIRC, no. I thought jails >> had low memory overhead, though. > > That's good, but memory overhead isn't the problem with a > jail. It's the diskspace used to duplicate everything > already available in /bin:/usr/bin:/usr/local/bin:... and > storage to hold the packages as things get built. > >> > If you only have 1 Gb of memory and 5-10 GB diskspace, >> > then using poudriere with zfs and jails is a nonstarter. >> >> For point of comparison, with those constraints, I do not >> understand how modern llvms can build at all. >> >> What happens if you use the manual approach on this same >> system? e.g. >> >> cd /usr/ports/devel/llvm40 >> mkdir -p /usr/ports/packages >> make && make package >> pkg install /usr/ports/packages/llvm.txz > > I normally do > > portmaster -Byd devel/llvm40 > > and wait a day for the build to complete. I have > /usr/ports/distfiles symlinked to a USB2 /mnt/distfiles > (40 MB/s max throughput). I may also need to set > DISABLE_MAKE_JOBS="YES", but can't remember offhand. > >> >> Do you still run out of resources? >> > > No. I have 4 GB of swap space, which is well used during the > build. The system is actually quite usable as portmaster > runs. I also build libreoffice and octave on the system. That must be fun ... At some point you'll run into the problem that even one copy of the ports that you want to install and just one copy of all their dependencies will no longer fit and then you have to start tossing out stuff that you would really like to install and use. I'm pretty sure that I no longer have enough room to build all the stuff on my laptop that I currently have installed (openoffice warns that it needs 11GB of free space). In that case, if you move the package building off to another machine, you don't even have to install many of the build dependencies on the target machine. For instance, I have a list of 214 ports that I want to install on my desktop machine. When I feed that into poudriere, it builds something on the order of 1900 ports. When I do the pkg install on my desktop machine with the same list, only 1431 packages get installed. >> In that case, there's not much that can be done. The >> compilers, the office suites, and certain math packages >> are huge beasts. However you try to build them won't >> matter. >> >> I would think having a copy of the llvm workfiles in a jail >> is going to be equivalent to having them in /tmp? >> >> I must be missing something. > > portmaster satisfies its dependencies from already installed > ports in /usr/local. There isn't a clean room full of pkg'd > dependencies sitting in some jail while llvm40 builds. The llvm40 problem should be helped a lot by subpackages. If you install a package that was built by llvm40 and uses its shared libraries, hopefully pkg will install a subpackage that contains the llvm40 .so files and not all of the compiler bits. You would only get those if you manually installed llvm40 so that you could use the compiler bits. In that case, poudriere would only cause two copies of the .so files to be installed and the compiler bits would only be installed on the machine (in the build jail) when poudriere was using a port that needed the llvm40 compiler. The same will be true of other things that are installed because of LIB_DEPENDS. Things like the include files, docs, and static libraries won't get automatically installed just because a port is a dependency of something else. They would only need to be manually installed if you want to build something manually outside of the ports framework. From owner-freebsd-ports@freebsd.org Thu Oct 5 01:14:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF18BE25FC0 for ; Thu, 5 Oct 2017 01:14:32 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BC3077D34D for ; Thu, 5 Oct 2017 01:14:32 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id BB8B9E25FBF; Thu, 5 Oct 2017 01:14:32 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB352E25FBE for ; Thu, 5 Oct 2017 01:14:32 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 18E2A7D349 for ; Thu, 5 Oct 2017 01:14:31 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 3f8e5808 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 4 Oct 2017 19:14:24 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: portmaster, portupgrade, etc From: Adam Weinberger In-Reply-To: <20171004161649.GA51883@mail.michaelwlucas.com> Date: Wed, 4 Oct 2017 19:14:22 -0600 Cc: ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20171004161649.GA51883@mail.michaelwlucas.com> To: "Michael W. Lucas" X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 01:14:32 -0000 > On 4 Oct, 2017, at 10:16, Michael W. Lucas = wrote: >=20 > Hi, >=20 > I'm doing tech edits on the new edition of "Absolute FreeBSD," and > stumbled into what's apparently a delicate topic. >=20 > Some of my reviewers are happy I included portmaster in the book. >=20 > Some reviewers beg me not to include it. >=20 > Unfortunately, people will be reading af3e and considering it > definitive for the next several years. So I have to get a feel for > where things are going. :-/ >=20 > I've read a couple threads on portmaster's current problems/growing > pains and its looming difficulty with forthcoming flavors. >=20 > I've been a happy portmaster user for many years now. All things being > equal, if its future is still being debated I'm inclined to keep it in > the book. >=20 > Poudriere really needs its own small book. Yes, you can do simple > poudriere installs, but once you start covering it properly the docs > quickly expand. My notes alone are longer than my af3e chapter > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > 2018). >=20 > Truly, I'm not looking to start a flame war here. I only want a bit of > guidance on The Future... >=20 > =3D=3Dml Hi Michael, Poudriere is indeed intended to be the canonical port building and = management tool. It is what essentially the entire ports committer team = uses, it's what the clusters build with, and it is where support for new = features land first. Portmaster is a tried-and-tested tool for automating port builds. = Poudriere wants to be everything to everybody, but portmaster is as = simple to use as possible. The current issue is that portmaster is no = longer actively developed. Major new features are about to land in the = ports tree, and portmaster will either not support them, or will break = entirely. The official message is that everybody for whom Poudriere's workflow = works should migrate to Poudriere to avoid the impending breakage. Portmaster is still very much a part of the current landscape, and if = somebody steps in to fix it (which I have every expectation will happen = eventually), it will continue being a usable alternative. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Oct 5 06:24:03 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D69BE2DEE9 for ; Thu, 5 Oct 2017 06:24:03 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 39C8F213E for ; Thu, 5 Oct 2017 06:24:03 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 391C0E2DEE7; Thu, 5 Oct 2017 06:24:03 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38B29E2DEE6 for ; Thu, 5 Oct 2017 06:24:03 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E3E5A213C for ; Thu, 5 Oct 2017 06:24:02 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id h63so7535897vka.4 for ; Wed, 04 Oct 2017 23:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bk1dqLqL8VESufBmSbOqCptI8EIPuse67pGcvNsHLiM=; b=eY15v9Y4o/bA7nCtRO9A48LKzUx4ZdeYQu3IsBgIzDfllGKOoBHoxJFhLw7EYusNPo 3kgPD8cVUEpOPHppsvJqv+5D8DenWIpA/k9fOZNQwDzcR9Pg2/7ahvub2yG+tYo4fkjj r9waR7sOdh59tba6RnDbr91MUFRxFH8qL0Sjub7/pl2f2rl4YvkInW0VEEtaNcqoGJit pOkichOQxmxgZa08Whk4Y4RGXqsTdEKcqd2JBaxx0L/8lKAgfObu/AlZH9qKxZBV6M0B aWaJ31Hh06atoPiH9HOLknXmI0Dlnaf67vv1mo+gKWzIn49rZXlfz4VNvDlN2UssMv7e oDbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bk1dqLqL8VESufBmSbOqCptI8EIPuse67pGcvNsHLiM=; b=D0aVYkkg1cLTLg2fg8CB8ln9jZPYlEXbfxgtL567hydp4E6Q4Kw5vA1kyGdxYWYcWE bdfQL2Aw5+symQxzuclyUvLN+OljrjB8SlMw3ZC4Vb7bJtPp/C5eQcZY4ng5I+1cbQsY ouiy7H3DDEuFNO4EXoklUNhRAX0w7C3wAarBGSy49nDbArINAvaInXlI0Bc3S3h8VPKf 5jBRBGGSHaCNWMXckpuqb8SYT8GK4sNiYN2VWLUlCYyXWS6po+Vi3fw2wmmF7t8soLBl fSZwb9p73XVFSkPbsewU80xayx2JhreWr3xawGcPvpkWxnPtaYRX/VkhA5+TRwwGnOYn WqhA== X-Gm-Message-State: AHPjjUiLnBbYUSf5+6omddEH8mhDEmJlJikjTVLRyHF9/723LVGFEcEs QkJk4kVMBiMKArgliXlL0HIsf6Ku8D/MtdZlfe4= X-Google-Smtp-Source: AOwi7QAZtYXdbN1qJBaVPVUQtLF7e9awU8uC1kx/Tmqw/g37/Max5VTqqjKeWC/250iQZbuNtD/Bn8bx3HlFlbqxeho= X-Received: by 10.31.206.3 with SMTP id e3mr12740250vkg.20.1507184641777; Wed, 04 Oct 2017 23:24:01 -0700 (PDT) MIME-Version: 1.0 References: <20171004161649.GA51883@mail.michaelwlucas.com> In-Reply-To: From: blubee blubeeme Date: Thu, 05 Oct 2017 06:23:50 +0000 Message-ID: Subject: Re: portmaster, portupgrade, etc To: Adam Weinberger , "Michael W. Lucas" Cc: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 06:24:03 -0000 Interesting thread, I've learned more about FreeBSD build here than almost anywhere else. Thanks OP for the email. On Thu, Oct 5, 2017, 09:14 Adam Weinberger wrote: > > On 4 Oct, 2017, at 10:16, Michael W. Lucas > wrote: > > > > Hi, > > > > I'm doing tech edits on the new edition of "Absolute FreeBSD," and > > stumbled into what's apparently a delicate topic. > > > > Some of my reviewers are happy I included portmaster in the book. > > > > Some reviewers beg me not to include it. > > > > Unfortunately, people will be reading af3e and considering it > > definitive for the next several years. So I have to get a feel for > > where things are going. :-/ > > > > I've read a couple threads on portmaster's current problems/growing > > pains and its looming difficulty with forthcoming flavors. > > > > I've been a happy portmaster user for many years now. All things being > > equal, if its future is still being debated I'm inclined to keep it in > > the book. > > > > Poudriere really needs its own small book. Yes, you can do simple > > poudriere installs, but once you start covering it properly the docs > > quickly expand. My notes alone are longer than my af3e chapter > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > > 2018). > > > > Truly, I'm not looking to start a flame war here. I only want a bit of > > guidance on The Future... > > > > ==ml > > Hi Michael, > > Poudriere is indeed intended to be the canonical port building and > management tool. It is what essentially the entire ports committer team > uses, it's what the clusters build with, and it is where support for new > features land first. > > Portmaster is a tried-and-tested tool for automating port builds. > Poudriere wants to be everything to everybody, but portmaster is as simple > to use as possible. The current issue is that portmaster is no longer > actively developed. Major new features are about to land in the ports tree, > and portmaster will either not support them, or will break entirely. > > The official message is that everybody for whom Poudriere's workflow works > should migrate to Poudriere to avoid the impending breakage. > > Portmaster is still very much a part of the current landscape, and if > somebody steps in to fix it (which I have every expectation will happen > eventually), it will continue being a usable alternative. > > # Adam > > > -- > Adam Weinberger > adamw@adamw.org > https://www.adamw.org > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Thu Oct 5 07:06:10 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0AD4E2ED97 for ; Thu, 5 Oct 2017 07:06:10 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 814F238F2 for ; Thu, 5 Oct 2017 07:06:10 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: by mailman.ysv.freebsd.org (Postfix) id 80978E2ED96; Thu, 5 Oct 2017 07:06:10 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 802C3E2ED94 for ; Thu, 5 Oct 2017 07:06:10 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F160238F0 for ; Thu, 5 Oct 2017 07:06:09 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v9575wHi032647 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 5 Oct 2017 09:05:59 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: fjwcash@gmail.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v9575twq038917; Thu, 5 Oct 2017 14:05:55 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: portmaster, portupgrade, etc To: Freddie Cash , Steve Kargl References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> Cc: FreeBSD Ports Mailing List , "Michael W. Lucas" From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <59D5D9D3.2070200@grosbein.net> Date: Thu, 5 Oct 2017 14:05:55 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 07:06:10 -0000 > Why compile ports directly on a box that is so hardware constrained that it > will take multiple hours to do, when a "pkg update; pkg upgrade" takes only > a few minutes? I tried really hard to run small virtual machine (1GB RAM, 25G disk) hosted at Hetzner without using ports and can say it's impossible. Pre-built packages from official repo are just too heavy and bloat the system with unneeded run-time dependencies not to mention impossibility to apply hot-fix in form of a patch. And running own repository is just not an option for such system. portupgrade (or analog) plus ZFS compressed svn-updates ports tree is lightest option in practice: zfs_load="YES" vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="8M" vfs.zfs.prefetch_disable="1" vfs.zfs.vdev.trim_on_init="0" vfs.zfs.compressed_arc_enabled="1" You can even run UFS-based system with /usr/ports mounted occasionally and zfs.ko/opensolaris.ko unloaded when not needed to free memory. From owner-freebsd-ports@freebsd.org Thu Oct 5 07:12:39 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51B5EE2EFAD for ; Thu, 5 Oct 2017 07:12:39 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C0CAB3D93 for ; Thu, 5 Oct 2017 07:12:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v957CTvh032689 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 5 Oct 2017 09:12:29 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: sgk@troutmask.apl.washington.edu Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v957CQls040860; Thu, 5 Oct 2017 14:12:26 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: portmaster, portupgrade, etc To: sgk@troutmask.apl.washington.edu, Grzegorz Junka References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171004181413.GA51148@troutmask.apl.washington.edu> <81df6e05-136a-0037-9dba-a7499b7820da@m5p.com> <20171004194025.GA10412@troutmask.apl.washington.edu> <20171004212225.GA26638@troutmask.apl.washington.edu> Cc: freebsd-ports@freebsd.org From: Eugene Grosbein Message-ID: <59D5DB5A.4090800@grosbein.net> Date: Thu, 5 Oct 2017 14:12:26 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20171004212225.GA26638@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 07:12:39 -0000 On 05.10.2017 04:22, Steve Kargl wrote: > I did not state that the "environment is constrained by poudriere". > The environment is contrained due to resource limits. If you > only have 1 Gb of memory and 5-10 GB diskspace, then using poudriere > with zfs and jails is a nonstarter. Yes, I'm aware that zfs is not > required. Can't find info on whether jails can be avoided. Having > say lang/llvm40 installed in /usr/local and in a jail would consumes > 2.6 GB. That's 1 port! In fact, a jail is not needed too. Just perform installworld to a /path, then mount -t devfs devfs /path/dev; mount -t nullfs /usr/ports /path/usr/ports and you are ready to build with chroot /path make -C /usr/ports/net/quagga package". Perhaps, you'll also need to setup /path/etc/resolv.conf unless you have caching DNS server running locally, so fetch(1) could download distfiles. From owner-freebsd-ports@freebsd.org Thu Oct 5 07:41:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99BE2E2F8C3 for ; Thu, 5 Oct 2017 07:41:14 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7A7F863CA0 for ; Thu, 5 Oct 2017 07:41:14 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by mailman.ysv.freebsd.org (Postfix) id 79D46E2F8C2; Thu, 5 Oct 2017 07:41:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79733E2F8C1 for ; Thu, 5 Oct 2017 07:41:14 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail.stromnet.se (s0.stromnet.se [109.74.15.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 356AD63C9E for ; Thu, 5 Oct 2017 07:41:13 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from mail (mail.j.stromnet.se [172.28.10.1]) by mail.stromnet.se (Postfix) with ESMTP id 7B7F1D7990; Thu, 5 Oct 2017 09:41:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=stromnet.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=default; t=1507189263; bh=pnw69p18ORhkSdzYTSRO7z+jK /NXWkU8SxVNv6yQcBk=; b=RViA7l+o8e+RHSNRLT4vQzTjgReFQKTLH29XHOxUR X88dEcBgvlxUAfPyOY2ypHyKAOS4cUUzZYeAlyonARsfjw5P9mJhA5XLb+hH83pN FXJ0e3ngPNClf3YCD0bmyBGPkxCEyvQ7mBS5IwvmH3rXxx+pyvq+DPKfu+nsVRe9 QCWkBnBaX79lDBfZ8v5v631drs2dtU9qxP1MDGXajNodC+7xhnFZ0SEL3E7vHCWr UQlJ8E0MIpyngKOlQcV+1Kq46R0NMWcplquovEn+8UCRuUl0NXeksdrqzN2ZdT9h W/hX/SvQG6eSvWsL2+e9iT3xFBM//qBkvd2zenhPRCEdQ== X-Virus-Scanned: amavisd-new at stromnet.se Received: from mail.stromnet.se ([172.28.10.1]) by mail (mail.stromnet.se [172.28.10.1]) (amavisd-new, port 10026) with ESMTP id 0c0KQCAc2Ybv; Thu, 5 Oct 2017 09:41:03 +0200 (CEST) Received: from johan-ht.stromnet.se (c-abfa70d5.019-333-67626721.cust.bredbandsbolaget.se [213.112.250.171]) by mail.stromnet.se (Postfix) with ESMTPSA id B875ED7968; Thu, 5 Oct 2017 09:41:03 +0200 (CEST) Subject: Re: FreeBSD telldusd port fix for devd script To: Hans Petter Selasky Cc: ports@FreeBSD.org References: <27b89374-5513-ed45-6ec1-58a2c1156543@selasky.org> <3bc6fa52-7066-05b9-2cdf-dfa8cfe681f9@stromnet.se> <7bdad62d-4897-c4ff-6e7a-c5362ccc131c@selasky.org> <03E2E2EC-85B6-4597-8F53-12B7E4F083F5@stromnet.se> <13c93a08-ecf0-fd4a-3a7b-3ba74c54d35b@selasky.org> From: =?UTF-8?Q?Johan_Str=c3=b6m?= Message-ID: <85124fb9-2cf4-7779-2f33-4b66bdaab054@stromnet.se> Date: Thu, 5 Oct 2017 09:41:03 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <13c93a08-ecf0-fd4a-3a7b-3ba74c54d35b@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 07:41:14 -0000 Hello again, cleaned up and submitted as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222790 Found that there was an old PR still hanging around with similar devd patch, which you had already provided, but it was never applied. Well, this one superseeds it :) Glad to hear it works 24/7! Same here, almost at least. Too bad upstream (Telldus) have stopped developing it, there are a few quirks that could be fixed such as On 04/10/17 16:51, Hans Petter Selasky wrote: > On 10/04/17 16:30, Johan Str=C3=B6m wrote: >> Ah, okay. Well, it works now and didn't work with the old devd rule, >> I'm happy with that :) >> >> Shall I create a patch and submit to bugzilla, or are you fixing this >> as part of bigger cleanup? > > Please submit it straight to ports. No more cleanup from my side at > the present. telldus is working great btw 24/7 ! > > --HPS > From owner-freebsd-ports@freebsd.org Thu Oct 5 07:48:11 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2FBFE2FA53 for ; Thu, 5 Oct 2017 07:48:11 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B561E64036 for ; Thu, 5 Oct 2017 07:48:11 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: by mailman.ysv.freebsd.org (Postfix) id B1589E2FA52; Thu, 5 Oct 2017 07:48:11 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF06DE2FA51 for ; Thu, 5 Oct 2017 07:48:11 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36EBB64035 for ; Thu, 5 Oct 2017 07:48:10 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v957llYG032892 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 5 Oct 2017 09:47:48 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: adamw@adamw.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v957liao051043; Thu, 5 Oct 2017 14:47:44 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: portmaster, portupgrade, etc To: Adam Weinberger , "Michael W. Lucas" References: <20171004161649.GA51883@mail.michaelwlucas.com> Cc: ports@freebsd.org From: Eugene Grosbein Message-ID: <59D5E3A0.8030608@grosbein.net> Date: Thu, 5 Oct 2017 14:47:44 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 07:48:11 -0000 On 05.10.2017 08:14, Adam Weinberger wrote: > Poudriere wants to be everything to everybody First poudriere will have to learn how to run without noticeable overhead compared to "just build from ports" before it could became "everything to everybody" and it needs to became part of base system for that purpose. From owner-freebsd-ports@freebsd.org Thu Oct 5 07:58:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A771E2FD69 for ; Thu, 5 Oct 2017 07:58:53 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E78436449F for ; Thu, 5 Oct 2017 07:58:52 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: by mailman.ysv.freebsd.org (Postfix) id E6CE5E2FD68; Thu, 5 Oct 2017 07:58:52 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6714E2FD67 for ; Thu, 5 Oct 2017 07:58:52 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD7F66449E for ; Thu, 5 Oct 2017 07:58:52 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (dslb-178-012-106-076.178.012.pools.vodafone-ip.de [178.12.106.76]) by host64.shmhost.net (Postfix) with ESMTPSA id 3348185CBB; Thu, 5 Oct 2017 09:58:48 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: portmaster, portupgrade, etc From: Franco Fichtner In-Reply-To: <59D5E3A0.8030608@grosbein.net> Date: Thu, 5 Oct 2017 09:58:47 +0200 Cc: Adam Weinberger , "Michael W. Lucas" , ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3183A82D-0425-4B57-8A12-B72A88892C62@lastsummer.de> References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D5E3A0.8030608@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-Spam-Flag: NO X-Spam-Score: -1.0 X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0 tests=[ALL_TRUSTED] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 07:58:53 -0000 > On 5. Oct 2017, at 9:47 AM, Eugene Grosbein = wrote: >=20 > On 05.10.2017 08:14, Adam Weinberger wrote: >=20 >> Poudriere wants to be everything to everybody >=20 > First poudriere will have to learn how to run without noticeable = overhead > compared to "just build from ports" before it could became "everything = to everybody" > and it needs to became part of base system for that purpose. For OPNsense we broke down the poudriere approach into a simple equivalent that is capable of building inside a jail, resume after a faulty build and wrap everything into a ready to use (pkg-repo creation and signing) archive that can be moved to a remote location and unpacked to be used as an online package repo, but it would also work on a singular system. https://github.com/opnsense/tools/blob/master/build/ports.sh In case someone feels the need to know this before starting from scratch trying to build something simple. It does not support clever multi-threading, but then again it would work as anyone would use the ports tree manually and runs well in a headless mode setting via cron for nightly rebuild fun. Cheers, Franco= From owner-freebsd-ports@freebsd.org Thu Oct 5 08:30:10 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 557D2E30A1E for ; Thu, 5 Oct 2017 08:30:10 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17D646557B for ; Thu, 5 Oct 2017 08:30:10 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Thu, 05 Oct 2017 10:29:25 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1507192198; bh=1nSTHtwkXKgKUW6Sf8jvRJlDCT8NuHnQ0R+biHH5zAQ=; h=Date:From:To:Subject:References:In-Reply-To; b=vvasCq28ZgeC3W7WS/paCK70QcE/mzEv0WEl8UGIUIgs7F1Q3/LalnlhhxBifcKqX dzNHw+CFi7m8TxttwX+PNFJVxZSU8ErBCfwSrrtokVo/zdfDOHPzvaO+YQZneGQKIo /U1nX0c/p21k1uAp+15SD3C5/o2qcQH44ayAcJEH1sBh3RKUCAkKi4Dmdjb1QksrSf 7MigAu7bcTm5uQg6EIVdjOCHDiW61qsXORboxxU6ZKBVbwfXlZZWKJisFZ+5RM1ZpG 6HydnAcd9tep6GfurpF0egk8wwSEW24Q20iRB7N+LEnzLI9u3u7PwG2ipfY0DERgBV tYfQycdpNO1Cw== Message-ID: <20171005102925.Horde.fBi3NGprAgvzMFIrxwyltHD@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc References: <20171004161649.GA51883@mail.michaelwlucas.com> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_WIIyq1gn8DRmSS1S-erdxHI"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 08:30:10 -0000 This message is in MIME format and has been PGP signed. --=_WIIyq1gn8DRmSS1S-erdxHI Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Adam Weinberger (from Wed, 4 Oct 2017=20=20 19:14:22=20-0600): > Portmaster is still very much a part of the current landscape, and=20=20 >=20if somebody steps in to fix it (which I have every expectation will=20= =20 >=20happen eventually), it will continue being a usable alternative. It would help to have a list of broken items in portmaster. I'm aware of the broken package support (can't create packages / can't=20= =20 use=20existing packages). Flavour/subpackages support? It would be nice to have a description=20=20 how=20it is supposed to work (how to identify the flavour in the package=20= =20 name=20/ port, how to detect subpackages in the package name / port, how=20= =20 to=20create a subpackage from a port, how to create a specific flavour=20= =20 from=20the port). What else? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_WIIyq1gn8DRmSS1S-erdxHI Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJZ1e1lAAoJEKrxQhqFIICEnbEP/i81vgov47jZvUzfzqSWZ4hQ LkUg9XwE/eE4qo3roxns7AocDcOL0YyLN7H7XIpbRMh4UCkhV2WeuOptf4D3GJL9 9Pn01MRCadOjaoRcpeydrpWRfmKiyKCvGabGYr1JTugmBwL3LC0xn0gONWCKvYQ0 cpLGkxxtO1kpQv4NEXtSS3R+ZtXQaiSkKWL8anbcK2leqeQLfdEdccRDrTqnmDAz Ghpn74+ldT84c/lbp3VPSeucLk5lmzYjlJUWZrE2b0K99sSgT40A5rnTci/vqGHR BItnF8FZv4J6AE4tvAKirAiy1W3JuJ4VdRvWzXCUnsxFBhXcZEvzUKK0PgJ95jGX M4Gtuu/mKh51jcbhVk9n+arYY6MslkEthUj0L8iU4Tew3op6Ybc2Z8+bD3h4HlAC ZY5wgs88jBoUA7UdN8u6IspHZ8X7riuufyq80hkknpA58EhdULOWQbWoIOy42qxm KwITNBxxCwbcC3g3f3PlDnRUa29G2Va7uIl+j4aPlFT/h54N+/si8+9gwpaKylj+ C1Bqhrr9XPXxa8KcBmJj003PA385AZ3gNFUBLGKZAmtvOAxru4DjmExSaCULpQbv tc+q6wMITpOGS436DyHcxdhiXcaAEMdUuhH2gZXeEwSQYe02VhVCo2O9mVLXdG/S 7MN2qOiu4r3Facy9z5M4 =lvtq -----END PGP SIGNATURE----- --=_WIIyq1gn8DRmSS1S-erdxHI-- From owner-freebsd-ports@freebsd.org Thu Oct 5 08:36:05 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 759D7E30D00 for ; Thu, 5 Oct 2017 08:36:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0BDC4659BD; Thu, 5 Oct 2017 08:36:04 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v958ZxcL057304 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 11:35:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v958ZxcL057304 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v958Zw9X057303; Thu, 5 Oct 2017 11:35:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Oct 2017 11:35:58 +0300 From: Konstantin Belousov To: Don Lewis Cc: sgk@troutmask.apl.washington.edu, linimon@lonesome.com, list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005083558.GD95911@kib.kiev.ua> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201710050027.v950RBFT047711@gw.catspoiler.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 08:36:05 -0000 On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: > > The system in question is my last i686 laptop, which I > > use for libm development and testing. Once I cannot use > > that laptop (whether hardware failure or inability to > > update the installed ports), I'll stop worrying about a > > functional libm on 32-bit hardware. > > As an aside, this sort of thing could be done in an i386 VM or maybe an > i386 jail on amd64 hardware. You do not need even a jail for this. Base cc -m32 works on amd64 for long time, and 32bit binaries can be executed from host environment, assuming all third-party libs are provided somewhere in the 32bit variant. The environment with regard to the hardware configuration should be identical to modern i386-arch machine with SSE2. Incompatibilities are considered as bugs and are usually fixed fast when reported. From owner-freebsd-ports@freebsd.org Thu Oct 5 09:08:02 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06DEFE31FD7 for ; Thu, 5 Oct 2017 09:08:02 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E40B966CB4 for ; Thu, 5 Oct 2017 09:08:01 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E3601E31FD4; Thu, 5 Oct 2017 09:08:01 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0F65E31FD2 for ; Thu, 5 Oct 2017 09:08:01 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D14FB66CB2 for ; Thu, 5 Oct 2017 09:08:01 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v95981F7051565 for ; Thu, 5 Oct 2017 09:08:01 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v959814R051559; Thu, 5 Oct 2017 09:08:01 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201710050908.v959814R051559@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 5 Oct 2017 09:08:01 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 09:08:02 -0000 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/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/aws-sdk-cpp | 1.2.5 | 1.2.8 ------------------------------------------------+-----------------+------------ misc/tkinfo | 2.8 | 2.9 ------------------------------------------------+-----------------+------------ 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 Thanks. From owner-freebsd-ports@freebsd.org Thu Oct 5 11:22:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EBEBE35366 for ; Thu, 5 Oct 2017 11:22:40 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from outmx-028.london.gridhost.co.uk (outmx-028.london.gridhost.co.uk [95.142.156.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF3816C2F9 for ; Thu, 5 Oct 2017 11:22:39 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk (unknown [82.71.56.121]) (Authenticated sender: mailpool@milibyte.co.uk) by outmx-028.london.gridhost.co.uk (Postfix) with ESMTPA id 7C75825A2A9B7 for ; Thu, 5 Oct 2017 12:15:42 +0100 (BST) Received: from [192.168.1.13] (helo=milibyte.co.uk) by curlew.milibyte.co.uk with esmtp (Exim 4.89) (envelope-from ) id 1e04EZ-0004gS-2a for freebsd-ports@freebsd.org; Thu, 05 Oct 2017 12:22:31 +0100 From: Mike Clarke To: freebsd-ports@freebsd.org Date: Thu, 05 Oct 2017 12:22:30 +0100 Message-ID: <1809004.bypIp25Zg3@curlew.lan> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <59D546FD.30906@gmail.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: portmaster, portupgrade, etc X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 11:22:40 -0000 On Wednesday 04 Oct 2017 16:39:25 Ernie Luzar wrote: > Here's my take on that. > > The future direction has already been decided by the FreeBSD leaders 2 > years ago with their development of a better pkg system. > > The package system with flavors will cover 90% of the user community > needs. The remaining user's requirements are edge cases. Tools like > portmaster and portupgrad and even the native ports system usage on > personal machines will fad away. The ports system will mature into the > development system in the path to get things into the package system. Well I suppose I fall into the remaining 10% of the user community so here's my two cents worth. I rely almost entirely on installing binary packages but I need to run php71 for compatibility with a website I maintain. I also need phpMyAdmin but need to build this from ports because the currently available package is built against php56. Using poudriere for this one task would be equivalent to using a steamroller to crack a peanut. Building phpMyAdmin from ports is no great problem for me and perhaps future development of pkg might avoid the need to build my own version but I'd hope that documented methods will continue to exist for users with this type of need. -- Mike Clarke From owner-freebsd-ports@freebsd.org Thu Oct 5 14:51:18 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60332E3A87B for ; Thu, 5 Oct 2017 14:51:18 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 393C17473F; Thu, 5 Oct 2017 14:51:18 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v95EpHnJ096308 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 07:51:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v95EpGsu096307; Thu, 5 Oct 2017 07:51:16 -0700 (PDT) (envelope-from sgk) Date: Thu, 5 Oct 2017 07:51:16 -0700 From: Steve Kargl To: Konstantin Belousov Cc: Don Lewis , linimon@lonesome.com, list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005145116.GA96180@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171005083558.GD95911@kib.kiev.ua> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 14:51:18 -0000 On Thu, Oct 05, 2017 at 11:35:58AM +0300, Konstantin Belousov wrote: > On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: > > > The system in question is my last i686 laptop, which I > > > use for libm development and testing. Once I cannot use > > > that laptop (whether hardware failure or inability to > > > update the installed ports), I'll stop worrying about a > > > functional libm on 32-bit hardware. > > > > As an aside, this sort of thing could be done in an i386 VM or maybe an > > i386 jail on amd64 hardware. > > You do not need even a jail for this. Base cc -m32 works on amd64 for > long time, and 32bit binaries can be executed from host environment, > assuming all third-party libs are provided somewhere in the 32bit > variant. > > The environment with regard to the hardware configuration should be > identical to modern i386-arch machine with SSE2. Incompatibilities are > considered as bugs and are usually fixed fast when reported. Does this required WITH_LIB32=yes in src.conf? More concerning is that the FPU on i686 is set-up in npx to use 53-bit precision instead of 64-bit. See x86/fpu.h where there is a large comment and the settings #define __INITIAL_FPUCW__ 0x037F #define __INITIAL_FPUCW_I386__ 0x127F #define __INITIAL_NPXCW__ __INITIAL_FPUCW_I386__ Does cc -m32 on amd64 cause the amd64 fpu to act (exactly?) like and i387? -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Thu Oct 5 14:59:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36781E3AB94 for ; Thu, 5 Oct 2017 14:59:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A67AD74B11; Thu, 5 Oct 2017 14:59:46 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v95Exf8C042911 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 17:59:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v95Exf8C042911 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v95Exfgj042910; Thu, 5 Oct 2017 17:59:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Oct 2017 17:59:41 +0300 From: Konstantin Belousov To: Steve Kargl Cc: Don Lewis , linimon@lonesome.com, list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005145941.GL95911@kib.kiev.ua> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171005145116.GA96180@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 14:59:47 -0000 On Thu, Oct 05, 2017 at 07:51:16AM -0700, Steve Kargl wrote: > On Thu, Oct 05, 2017 at 11:35:58AM +0300, Konstantin Belousov wrote: > > On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: > > > > The system in question is my last i686 laptop, which I > > > > use for libm development and testing. Once I cannot use > > > > that laptop (whether hardware failure or inability to > > > > update the installed ports), I'll stop worrying about a > > > > functional libm on 32-bit hardware. > > > > > > As an aside, this sort of thing could be done in an i386 VM or maybe an > > > i386 jail on amd64 hardware. > > > > You do not need even a jail for this. Base cc -m32 works on amd64 for > > long time, and 32bit binaries can be executed from host environment, > > assuming all third-party libs are provided somewhere in the 32bit > > variant. > > > > The environment with regard to the hardware configuration should be > > identical to modern i386-arch machine with SSE2. Incompatibilities are > > considered as bugs and are usually fixed fast when reported. > > Does this required WITH_LIB32=yes in src.conf? Yes, but this is the default. > > More concerning is that the FPU on i686 is set-up in npx to > use 53-bit precision instead of 64-bit. See x86/fpu.h where > there is a large comment and the settings > > #define __INITIAL_FPUCW__ 0x037F > #define __INITIAL_FPUCW_I386__ 0x127F > #define __INITIAL_NPXCW__ __INITIAL_FPUCW_I386__ > > Does cc -m32 on amd64 cause the amd64 fpu to act (exactly?) like > and i387? It is not cc -m32. Kernel sets up x87 FPU differently for 64 and 32bit processes. See ia32_setregs() where pcb is adjusted for 32bit, and r189423. From owner-freebsd-ports@freebsd.org Thu Oct 5 15:25:21 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AEEDE3B414 for ; Thu, 5 Oct 2017 15:25:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 34E5B75DEF; Thu, 5 Oct 2017 15:25:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v95FPKro096603 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 08:25:20 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v95FPKaT096602; Thu, 5 Oct 2017 08:25:20 -0700 (PDT) (envelope-from sgk) Date: Thu, 5 Oct 2017 08:25:20 -0700 From: Steve Kargl To: Konstantin Belousov Cc: linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005152520.GA96545@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171005145941.GL95911@kib.kiev.ua> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 15:25:21 -0000 On Thu, Oct 05, 2017 at 05:59:41PM +0300, Konstantin Belousov wrote: > On Thu, Oct 05, 2017 at 07:51:16AM -0700, Steve Kargl wrote: > > On Thu, Oct 05, 2017 at 11:35:58AM +0300, Konstantin Belousov wrote: > > > On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: > > > > > The system in question is my last i686 laptop, which I > > > > > use for libm development and testing. Once I cannot use > > > > > that laptop (whether hardware failure or inability to > > > > > update the installed ports), I'll stop worrying about a > > > > > functional libm on 32-bit hardware. > > > > > > > > As an aside, this sort of thing could be done in an i386 VM or maybe an > > > > i386 jail on amd64 hardware. > > > > > > You do not need even a jail for this. Base cc -m32 works on amd64 for > > > long time, and 32bit binaries can be executed from host environment, > > > assuming all third-party libs are provided somewhere in the 32bit > > > variant. > > > > > > The environment with regard to the hardware configuration should be > > > identical to modern i386-arch machine with SSE2. Incompatibilities are > > > considered as bugs and are usually fixed fast when reported. > > > > Does this required WITH_LIB32=yes in src.conf? > Yes, but this is the default. > > > > > More concerning is that the FPU on i686 is set-up in npx to > > use 53-bit precision instead of 64-bit. See x86/fpu.h where > > there is a large comment and the settings > > > > #define __INITIAL_FPUCW__ 0x037F > > #define __INITIAL_FPUCW_I386__ 0x127F > > #define __INITIAL_NPXCW__ __INITIAL_FPUCW_I386__ > > > > Does cc -m32 on amd64 cause the amd64 fpu to act (exactly?) like > > and i387? > It is not cc -m32. > > Kernel sets up x87 FPU differently for 64 and 32bit processes. See > ia32_setregs() where pcb is adjusted for 32bit, and r189423. Yes, I know the kernel sets up npx on i686. If one is testing libm changes or new code for libm, then cc -m32 will be insufficient in testing the behavior one might get from i387 in 53-bit mode as oppose to 64-bit. This is the reason the macro LD80C exists in math_private.h. Which brings me back to my i686 laptop with limited resources. If portmgr makes it impractical/impossible to easily install ports without a sledge hammer, then testing possible future patches to libm will simply skip i686 class hardware. -- Steve From owner-freebsd-ports@freebsd.org Thu Oct 5 15:31:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 057B3E3B595 for ; Thu, 5 Oct 2017 15:31:51 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99E2376165; Thu, 5 Oct 2017 15:31:49 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id c6c0d981 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 5 Oct 2017 09:31:45 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: portmaster, portupgrade, etc From: Adam Weinberger In-Reply-To: <20171005152520.GA96545@troutmask.apl.washington.edu> Date: Thu, 5 Oct 2017 09:31:41 -0600 Cc: Konstantin Belousov , linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> To: sgk@troutmask.apl.washington.edu X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 15:31:51 -0000 > On 5 Oct, 2017, at 9:25, Steve Kargl = wrote: >=20 > On Thu, Oct 05, 2017 at 05:59:41PM +0300, Konstantin Belousov wrote: >> On Thu, Oct 05, 2017 at 07:51:16AM -0700, Steve Kargl wrote: >>> On Thu, Oct 05, 2017 at 11:35:58AM +0300, Konstantin Belousov wrote: >>>> On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: >>>>>> The system in question is my last i686 laptop, which I=20 >>>>>> use for libm development and testing. Once I cannot use >>>>>> that laptop (whether hardware failure or inability to=20 >>>>>> update the installed ports), I'll stop worrying about a >>>>>> functional libm on 32-bit hardware. >>>>>=20 >>>>> As an aside, this sort of thing could be done in an i386 VM or = maybe an >>>>> i386 jail on amd64 hardware. >>>>=20 >>>> You do not need even a jail for this. Base cc -m32 works on amd64 = for >>>> long time, and 32bit binaries can be executed from host = environment, >>>> assuming all third-party libs are provided somewhere in the 32bit >>>> variant. >>>>=20 >>>> The environment with regard to the hardware configuration should be >>>> identical to modern i386-arch machine with SSE2. Incompatibilities = are >>>> considered as bugs and are usually fixed fast when reported. >>>=20 >>> Does this required WITH_LIB32=3Dyes in src.conf? >> Yes, but this is the default. >>=20 >>>=20 >>> More concerning is that the FPU on i686 is set-up in npx to >>> use 53-bit precision instead of 64-bit. See x86/fpu.h where >>> there is a large comment and the settings >>>=20 >>> #define __INITIAL_FPUCW__ 0x037F >>> #define __INITIAL_FPUCW_I386__ 0x127F >>> #define __INITIAL_NPXCW__ __INITIAL_FPUCW_I386__ >>>=20 >>> Does cc -m32 on amd64 cause the amd64 fpu to act (exactly?) like >>> and i387? >> It is not cc -m32. >>=20 >> Kernel sets up x87 FPU differently for 64 and 32bit processes. See >> ia32_setregs() where pcb is adjusted for 32bit, and r189423. >=20 > Yes, I know the kernel sets up npx on i686. If one is testing libm > changes or new code for libm, then cc -m32 will be insufficient in > testing the behavior one might get from i387 in 53-bit mode as=20 > oppose to 64-bit. This is the reason the macro LD80C exists in > math_private.h. >=20 > Which brings me back to my i686 laptop with limited resources. > If portmgr makes it impractical/impossible to easily install ports > without a sledge hammer, then testing possible future patches to=20 > libm will simply skip i686 class hardware. I'm not clear what role you think portmgr has in this. Portmgr merely = brings new features to the ports tree. Portmgr itself is responsible for = no build tool other than "make install". I don't know how many times I need to keep saying this, but portmgr is = not killing off portmaster. There is simply nobody developing portmaster = anymore, and that is not portmgr's responsibility. There ARE people = developing poudriere, and that is why poudriere continues to work with = new ports tree features. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Oct 5 15:58:36 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0356FE3BDC4 for ; Thu, 5 Oct 2017 15:58:36 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92B3A76F10; Thu, 5 Oct 2017 15:58:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v95FwQjr056512 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 18:58:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v95FwQjr056512 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v95FwPgL056511; Thu, 5 Oct 2017 18:58:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 5 Oct 2017 18:58:25 +0300 From: Konstantin Belousov To: Steve Kargl Cc: linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005155825.GM95911@kib.kiev.ua> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171005152520.GA96545@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 15:58:36 -0000 On Thu, Oct 05, 2017 at 08:25:20AM -0700, Steve Kargl wrote: > On Thu, Oct 05, 2017 at 05:59:41PM +0300, Konstantin Belousov wrote: > > On Thu, Oct 05, 2017 at 07:51:16AM -0700, Steve Kargl wrote: > > > On Thu, Oct 05, 2017 at 11:35:58AM +0300, Konstantin Belousov wrote: > > > > On Wed, Oct 04, 2017 at 05:27:11PM -0700, Don Lewis wrote: > > > > > > The system in question is my last i686 laptop, which I > > > > > > use for libm development and testing. Once I cannot use > > > > > > that laptop (whether hardware failure or inability to > > > > > > update the installed ports), I'll stop worrying about a > > > > > > functional libm on 32-bit hardware. > > > > > > > > > > As an aside, this sort of thing could be done in an i386 VM or maybe an > > > > > i386 jail on amd64 hardware. > > > > > > > > You do not need even a jail for this. Base cc -m32 works on amd64 for > > > > long time, and 32bit binaries can be executed from host environment, > > > > assuming all third-party libs are provided somewhere in the 32bit > > > > variant. > > > > > > > > The environment with regard to the hardware configuration should be > > > > identical to modern i386-arch machine with SSE2. Incompatibilities are > > > > considered as bugs and are usually fixed fast when reported. > > > > > > Does this required WITH_LIB32=yes in src.conf? > > Yes, but this is the default. > > > > > > > > More concerning is that the FPU on i686 is set-up in npx to > > > use 53-bit precision instead of 64-bit. See x86/fpu.h where > > > there is a large comment and the settings > > > > > > #define __INITIAL_FPUCW__ 0x037F > > > #define __INITIAL_FPUCW_I386__ 0x127F > > > #define __INITIAL_NPXCW__ __INITIAL_FPUCW_I386__ > > > > > > Does cc -m32 on amd64 cause the amd64 fpu to act (exactly?) like > > > and i387? > > It is not cc -m32. > > > > Kernel sets up x87 FPU differently for 64 and 32bit processes. See > > ia32_setregs() where pcb is adjusted for 32bit, and r189423. > > Yes, I know the kernel sets up npx on i686. If one is testing libm > changes or new code for libm, then cc -m32 will be insufficient in > testing the behavior one might get from i387 in 53-bit mode as > oppose to 64-bit. This is the reason the macro LD80C exists in > math_private.h. Again, if there is any bug in setting FPU environment for 32bit process, i.e. an inconsistency between native i386 kernel and compat32 on amd64, explain it or better, provide the test case. It will be fixed quickly. Currently I am not aware of any. > > Which brings me back to my i686 laptop with limited resources. > If portmgr makes it impractical/impossible to easily install ports > without a sledge hammer, then testing possible future patches to > libm will simply skip i686 class hardware. > > -- > Steve From owner-freebsd-ports@freebsd.org Thu Oct 5 16:06:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B765AE3C059 for ; Thu, 5 Oct 2017 16:06:49 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 860B37735B for ; Thu, 5 Oct 2017 16:06:49 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 384caa56 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Thu, 5 Oct 2017 09:06:48 -0700 (PDT) To: freebsd-ports@freebsd.org From: Pete Wright Subject: collectd5 pkg upgrade pulls in 72 new dependencies? Message-ID: <2ce0d4f8-5f45-e237-e6f7-32b8e9fac736@nomadlogic.org> Date: Thu, 5 Oct 2017 09:06:47 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 16:06:49 -0000 hey there - i was doing usual maintaince on my systems today and noticed that when upgrading the collectd5 pkg it pulls in 72 new dependencies, mostly xorg related.  here's a gist of the upgrade command exhibiting this.  the platform 11.1-RELEASE: https://gist.github.com/nomadlogic/53e81ba377a4a475351c3b8309be7598 is this expected?  maybe i missed a heads up email to this list? cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-ports@freebsd.org Thu Oct 5 16:28:55 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2A58E3C6C0 for ; Thu, 5 Oct 2017 16:28:55 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BCB2B77E27; Thu, 5 Oct 2017 16:28:55 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v95GSrFK096999 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 09:28:53 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v95GSrid096998; Thu, 5 Oct 2017 09:28:53 -0700 (PDT) (envelope-from sgk) Date: Thu, 5 Oct 2017 09:28:53 -0700 From: Steve Kargl To: Adam Weinberger Cc: Konstantin Belousov , linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005162853.GA96784@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 16:28:56 -0000 On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: > > On 5 Oct, 2017, at 9:25, Steve Kargl wrote: > > Which brings me back to my i686 laptop with limited resources. > > If portmgr makes it impractical/impossible to easily install ports > > without a sledge hammer, then testing possible future patches to > > libm will simply skip i686 class hardware. > > I'm not clear what role you think portmgr has in this. Portmgr > merely brings new features to the ports tree. Portmgr itself is > responsible for no build tool other than "make install". > > I don't know how many times I need to keep saying this, but > portmgr is not killing off portmaster. There is simply nobody > developing portmaster anymore, and that is not portmgr's > responsibility. There ARE people developing poudriere, and > that is why poudriere continues to work with new ports tree features. > I suppose it's a matter of semantics. If the Makefiles and *.mk files under /usr/ports are altered to allow subpackages and flavours to enhance pkg and poudriere, which will break portmaster further, then yes portmgr has made a decision to endorse a sledge hammer over simple tools. Mere users of the ports collection are not privy to discussions on a portmgr alias/mailinglist. A quick scan of the members of portmgr and contributors to poudriere show at least 4 common members. There are 8 people listed under portmgr. When decisions were being made on the introduction of subpackages/flavours into the ports collection, did the 4 common members recluse themselves from any formal or informal vote? If no, then there is certainly a conflict-of-interest in what is best for the ports collection versus what is best for poudriere. Yes, portmaster is currently unmaintained. Doug Barton left FreeBSD developement because he was continually brow beaten whenever he pointed out what he felt were (serious) flaws in FreeBSD and in the ports collection. -- Steve From owner-freebsd-ports@freebsd.org Thu Oct 5 16:52:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46639E3D12B for ; Thu, 5 Oct 2017 16:52:59 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 283547D43E; Thu, 5 Oct 2017 16:52:55 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id fc133fdb TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 5 Oct 2017 10:52:53 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: portmaster, portupgrade, etc From: Adam Weinberger In-Reply-To: <20171005162853.GA96784@troutmask.apl.washington.edu> Date: Thu, 5 Oct 2017 10:52:51 -0600 Cc: Konstantin Belousov , linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> To: sgk@troutmask.apl.washington.edu X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 16:52:59 -0000 > On 5 Oct, 2017, at 10:28, Steve Kargl = wrote: >=20 > On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: >>> On 5 Oct, 2017, at 9:25, Steve Kargl = wrote: >>> Which brings me back to my i686 laptop with limited resources. >>> If portmgr makes it impractical/impossible to easily install ports >>> without a sledge hammer, then testing possible future patches to=20 >>> libm will simply skip i686 class hardware. >>=20 >> I'm not clear what role you think portmgr has in this. Portmgr >> merely brings new features to the ports tree. Portmgr itself is >> responsible for no build tool other than "make install". >>=20 >> I don't know how many times I need to keep saying this, but >> portmgr is not killing off portmaster. There is simply nobody >> developing portmaster anymore, and that is not portmgr's >> responsibility. There ARE people developing poudriere, and >> that is why poudriere continues to work with new ports tree features. >>=20 >=20 > I suppose it's a matter of semantics. If the Makefiles and *.mk > files under /usr/ports are altered to allow subpackages and > flavours to enhance pkg and poudriere, which will break portmaster > further, then yes portmgr has made a decision to endorse a sledge > hammer over simple tools. >=20 > Mere users of the ports collection are not privy to discussions > on a portmgr alias/mailinglist. A quick scan of the members of=20 > portmgr and contributors to poudriere show at least 4 common > members. There are 8 people listed under portmgr. When decisions > were being made on the introduction of subpackages/flavours into > the ports collection, did the 4 common members recluse themselves > from any formal or informal vote? If no, then there is certainly > a conflict-of-interest in what is best for the ports collection > versus what is best for poudriere. >=20 > Yes, portmaster is currently unmaintained. Doug Barton left > FreeBSD developement because he was continually brow beaten > whenever he pointed out what he felt were (serious) flaws in > FreeBSD and in the ports collection. Not quite. It works in the other direction. Ports isn't designed for = poudriere. Poudriere is designed for ports. 100% of the flavours = development is happening in public. Anybody who wishes to work on = portmaster can participate in the process too. I think you have a misperception of the relationship between portmgr and = poudriere. The coming flavours would break poudriere too, except there = are people actively developing it. You seem to be fully convinced in a conspiracy to destroy portmaster, = and I don't get the impression that I'm going to change your mind. All I = can tell you is that impending portmaster breakage is NOT by design, and = is only happening because portmaster isn't actively developed anymore. = If you'd like to believe in secret poudriere cabals and anti-portmaster = conspiracies, that's up to you. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Oct 5 18:41:32 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9924E3F497 for ; Thu, 5 Oct 2017 18:41:32 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 706ED80F30; Thu, 5 Oct 2017 18:41:32 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v95IfPm6097982 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Oct 2017 11:41:25 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v95IfOwj097981; Thu, 5 Oct 2017 11:41:24 -0700 (PDT) (envelope-from sgk) Date: Thu, 5 Oct 2017 11:41:18 -0700 From: Steve Kargl To: Adam Weinberger Cc: Konstantin Belousov , linimon@lonesome.com, Don Lewis , list1@gjunka.com, freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005184118.GA97889@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 18:41:32 -0000 On Thu, Oct 05, 2017 at 10:52:51AM -0600, Adam Weinberger wrote: (courtesy long-line wrap) > You seem to be fully convinced in a conspiracy to destroy > portmaster, and I don't get the impression that I'm going > to change your mind. All I can tell you is that impending > portmaster breakage is NOT by design, and is only happening > because portmaster isn't actively developed anymore. If > you'd like to believe in secret poudriere cabals and > anti-portmaster conspiracies, that's up to you. Nope. No conspiracy theory here. But, the above is a good method to deflect attention and blame. I simply find it ironic/comical that someone dreamt up flavours/subpackage for the ports collections with the knowledge that this will break all tools used to manage ports, and portmgr which is charged with Discusses how that the way that the Ports Collection is implemented affects the above policies, and, in particular, such concepts as changes that require regression tests and sweeping changes. (see https://www.freebsd.org/portmgr/) seems to have endorsed a "sweeping change" with this outcome. Then that someone managed to convince developers of a single ports management tool to implement support for flavours/subpackaged. So, portmgr now is going ahead with a "sweeping change" at the expense of all other ports management tool. I have simply pointed out, portmgr and contributors to that single ports manange tool have a significant overlap. Nope. No conspiracy. Just the truth. So, Adam, if the poudriere developers had stated that poudriere would not support flavors/subpackages would portmgr still wedge the necessary infrastructure into the Makefiles and *.mk files? -- Steve From owner-freebsd-ports@freebsd.org Thu Oct 5 19:54:38 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C2E0E4124E for ; Thu, 5 Oct 2017 19:54:38 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3ABA784957 for ; Thu, 5 Oct 2017 19:54:37 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.81.207]) by cmsmtp with ESMTP id 0CE5eMUCMeXb60CE7ea8Uh; Thu, 05 Oct 2017 19:54:36 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1e0CE5-0006bL-34 for freebsd-ports@freebsd.org; Thu, 05 Oct 2017 19:54:33 +0000 Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> From: Baho Utot Message-ID: Date: Thu, 5 Oct 2017 15:54:32 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <59D546FD.30906@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfLbF65VNPAx2UKR5VDEDEHqsuxWV72x9krlYVmGQCZbXCqwk7RgyHdGxm1rzcLZC/JjDW3arhu32ReFJ8WVX35yyH8HwCfzvsq5gI0wtJ6PYIyn3XPBv h7BUKDSXO9ad8QXdXrztEBhC09WbAtKt14J8s0bIJKma79BpUVR2cAiZVPwNhgMBjKCNfiwA4rP757I85aPb7w5CeVlKzemPBA8= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 19:54:38 -0000 On 10/04/17 16:39, Ernie Luzar wrote: > Here's my take on that. > > The future direction has already been decided by the FreeBSD leaders 2 > years ago with their development of a better pkg system. > [putolin] > Don't let the few old school die hearts who are afraid of any change and > make the most noise influence you. There will always be edge case user > who think their needs out weight what is best for the group. So what you are really saying is Go to hell old farts we don't need you here. We are not going to listen to you as you are too old to know anything. You are old and stupid. It is looking like I will need to move away from FreeBSD if that is really what is being accomplished here. > > Remember that your updated book will become a bible for many years and > many readers. Don't include items that are now on the edge of being > replaced. > > Another candidate is JAILs  IE: the old way of jail definition was in > rc.conf the new way being jail.conf. The jail.conf method was > introduction was at RELEASE 9.0 and here its 11.1 and still the old > school users fight to retain both ways. Hoping that with 12.0, support > for jail definition in rc.conf will be totally removed. > > One last though. The problem with the Freebsd handbook is that it reads > like a list of reminder notes. The reader is expected to already have a > well defined understanding of the subject being read about. The past 2 > years a great amount of effort has gone into bring the handbook up to > date with the current status of the operating system. But it is a very > far cry from a teaching aid. > > Please take the time to rework the original "Absolute FreeBSD" content > into something that is usable as a teaching book. You must assume that > the only thing the reader knows about Freebsd is how to spell the word > Freebsd and build the content from there. > > Good luck. > > > > > > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 20:24:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BB96E41CA5 for ; Thu, 5 Oct 2017 20:24:14 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24AD8BD3 for ; Thu, 5 Oct 2017 20:24:13 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x2f7ff22.dyn.telefonica.de [2.247.255.34]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95KO5n6061948 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 20:24:06 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x2f7ff22.dyn.telefonica.de [2.247.255.34] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <20171005184118.GA97889@troutmask.apl.washington.edu> From: Grzegorz Junka Message-ID: <0d2e2a5e-fa78-81ad-ec39-eaaf06fd133f@gjunka.com> Date: Thu, 5 Oct 2017 20:24:00 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171005184118.GA97889@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 20:24:14 -0000 On 05/10/2017 18:41, Steve Kargl wrote: > On Thu, Oct 05, 2017 at 10:52:51AM -0600, Adam Weinberger wrote: > > (courtesy long-line wrap) > >> You seem to be fully convinced in a conspiracy to destroy >> portmaster, and I don't get the impression that I'm going >> to change your mind. All I can tell you is that impending >> portmaster breakage is NOT by design, and is only happening >> because portmaster isn't actively developed anymore. If >> you'd like to believe in secret poudriere cabals and >> anti-portmaster conspiracies, that's up to you. > Nope. No conspiracy theory here. But, the above is a good > method to deflect attention and blame. > > I simply find it ironic/comical that someone dreamt up > flavours/subpackage for the ports collections with the > knowledge that this will break all tools used to manage > ports, and portmgr which is charged with > > Discusses how that the way that the Ports Collection is > implemented affects the above policies, and, in particular, > such concepts as changes that require regression tests and > sweeping changes. > > (see https://www.freebsd.org/portmgr/) seems to have endorsed > a "sweeping change" with this outcome. > > Then that someone managed to convince developers of a single > ports management tool to implement support for flavours/subpackaged. > So, portmgr now is going ahead with a "sweeping change" at the expense > of all other ports management tool. I have simply pointed out, portmgr > and contributors to that single ports manange tool have a significant > overlap. Nope. No conspiracy. Just the truth. > > So, Adam, if the poudriere developers had stated that poudriere > would not support flavors/subpackages would portmgr still wedge > the necessary infrastructure into the Makefiles and *.mk files? > I don't understand this argument. Are flavours / subpackages good / desirable or they are not good / undesirable? As far as I know they enable features that otherwise wouldn't be possible. So surely not the later. So if the former, could they have been designed in a way that doesn't break existing build tools? Maybe yes, but if that was the case then surely someone would have proposed such a design? Or maybe even implemented it. Maybe at an additional cost of non-trivial changes somewhere else. Maybe updating the build tools was the easier option. In the end those are just build tools and no one should expect them to never change. But if that was the case, how would they go about updating ports to support new features? Of course, they would discuss with the maintainers of those tools, (why wouldn't they ?), if the change is feasible to implement in the tools and would take less effort than the mentioned change somewhere else instead. How many maintainers they would need to contact? I know of 4 - portmaster, portupgrade, synth and poudriere. Am I missing something? Oh, yes, the mighty make. But it will be mass-updated so no need to look for anyone. So, who should they contact to discuss the support for ports/subpackages in portmaster, portupgrade and synth? Should they hold off until a maintainer is found? Should they pay for updating these tools from their pocket (using their time)? GrzegorzJ From owner-freebsd-ports@freebsd.org Thu Oct 5 20:27:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 792F7E41D41 for ; Thu, 5 Oct 2017 20:27:28 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 23D7CCC3 for ; Thu, 5 Oct 2017 20:27:27 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x2f7ff22.dyn.telefonica.de [2.247.255.34]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95KRON7062022 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 20:27:25 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x2f7ff22.dyn.telefonica.de [2.247.255.34] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> From: Grzegorz Junka Message-ID: Date: Thu, 5 Oct 2017 20:27:19 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 20:27:28 -0000 On 05/10/2017 19:54, Baho Utot wrote: > > > On 10/04/17 16:39, Ernie Luzar wrote: > >> Here's my take on that. >> >> The future direction has already been decided by the FreeBSD leaders >> 2 years ago with their development of a better pkg system. >> > > [putolin] > >> Don't let the few old school die hearts who are afraid of any change >> and make the most noise influence you. There will always be edge case >> user who think their needs out weight what is best for the group. > > So what you are really saying is Go to hell old farts we don't need > you here. We are not going to listen to you as you are too old to > know anything. You are old and stupid. > > It is looking like I will need to move away from FreeBSD if that is > really what is being accomplished here. But do those old farts have anything interesting to say or they are just making noise? What's the alternative to the proposed direction? GrzegorzJ From owner-freebsd-ports@freebsd.org Thu Oct 5 21:49:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68F56E435DA for ; Thu, 5 Oct 2017 21:49:29 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4180C3BC4 for ; Thu, 5 Oct 2017 21:49:28 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95LrZH6017125 for ; Thu, 5 Oct 2017 14:53:41 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu>, From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 14:53:41 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 21:49:29 -0000 On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote > > On 5 Oct, 2017, at 10:28, Steve Kargl > > wrote: > > On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: > >>> On 5 Oct, 2017, at 9:25, Steve Kargl > >>> wrote: Which brings me back to my i686 laptop with limited resources. > >>> If portmgr makes it impractical/impossible to easily install ports > >>> without a sledge hammer, then testing possible future patches to > >>> libm will simply skip i686 class hardware. > >> > >> I'm not clear what role you think portmgr has in this. Portmgr > >> merely brings new features to the ports tree. Portmgr itself is > >> responsible for no build tool other than "make install". > >> > >> I don't know how many times I need to keep saying this, but > >> portmgr is not killing off portmaster. There is simply nobody > >> developing portmaster anymore, and that is not portmgr's > >> responsibility. There ARE people developing poudriere, and > >> that is why poudriere continues to work with new ports tree features. > >> > > > > I suppose it's a matter of semantics. If the Makefiles and *.mk > > files under /usr/ports are altered to allow subpackages and > > flavours to enhance pkg and poudriere, which will break portmaster > > further, then yes portmgr has made a decision to endorse a sledge > > hammer over simple tools. > > > > Mere users of the ports collection are not privy to discussions > > on a portmgr alias/mailinglist. A quick scan of the members of > > portmgr and contributors to poudriere show at least 4 common > > members. There are 8 people listed under portmgr. When decisions > > were being made on the introduction of subpackages/flavours into > > the ports collection, did the 4 common members recluse themselves > > from any formal or informal vote? If no, then there is certainly > > a conflict-of-interest in what is best for the ports collection > > versus what is best for poudriere. > > > > Yes, portmaster is currently unmaintained. Doug Barton left > > FreeBSD developement because he was continually brow beaten > > whenever he pointed out what he felt were (serious) flaws in > > FreeBSD and in the ports collection. > > Not quite. It works in the other direction. Ports isn't designed for > poudriere. Poudriere is designed for ports. 100% of the flavours development > is happening in public. Anybody who wishes to work on portmaster can > participate in the process too. > > I think you have a misperception of the relationship between portmgr and > poudriere. The coming flavours would break poudriere too, except there are > people actively developing it. > > You seem to be fully convinced in a conspiracy to destroy portmaster, and I > don't get the impression that I'm going to change your mind. All I can tell > you is that impending portmaster breakage is NOT by design, and is only > happening because portmaster isn't actively developed anymore. If you'd like > to believe in secret poudriere cabals and anti-portmaster conspiracies, > that's up to you. > > # Adam While I have no intention to speak on Steve's behalf. I /would/ like to speak in his humble defense; over year ago, I attempted to become maintainer for ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in it's value, and 2) it had been scorned for some time, and there were /many/ discussions to have it removed. At the time I attempted the request, it had not "officially" had a maintainer, and there was serious talk as to /really/ having it removed from the ports tree. bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the mailing list for portmaster /will/ show /many/ heated discussions regarding it's removal -- this thread included. In any event, after a few inquiries regarding taking maintainer for the port. My request was ultimately declined. I was deemed unqualified. That judgement was unfounded. :( Granted, maintenance of portmaster is no small feat -- it's an enormous scriptbal. But now some months later, I am maintainer for ~120 ports! perform a search for portmaster@ and see for yourself. You can say what you will about some of those ports, but what it /does/ show, is commitment, and long term commitment to boot! I grow weary of the circular discussions surrounding portmaster. So this is what I'd like to propose. It's maintenance is a bigger job for anyone whom is not it's original author, for anyone that did not grow it from scratch, and become so intimately familiar with it. So perhaps a better solution might be for me to attempt again ask to become maintainer. But this time, make it a group effort -- if for no other reason, for my own sanity. But better; that it can/will be more promptly addressed. IOW problems that arise, can more easily be addressed when a group of individuals are involved with it's maintenance. Seem a reasonable request? If [found] so, I'll solicit for qualified individuals to work with me on it in a new thread. Thanks for your time, and consideration --Chris > > > -- > Adam Weinberger > adamw@adamw.org > https://www.adamw.org > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 21:59:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63AB4E439C0 for ; Thu, 5 Oct 2017 21:59:59 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 191C1633A2 for ; Thu, 5 Oct 2017 21:59:58 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95M4BZJ017960 for ; Thu, 5 Oct 2017 15:04:17 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com>, From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 15:04:17 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2ba9c615d1d6f66e65590e84a0c91458@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 21:59:59 -0000 On Thu, 5 Oct 2017 15:54:32 -0400 Baho Utot wrote > On 10/04/17 16:39, Ernie Luzar wrote: > > > Here's my take on that. > > > > The future direction has already been decided by the FreeBSD leaders 2 > > years ago with their development of a better pkg system. > > > > [putolin] > > > Don't let the few old school die hearts who are afraid of any change and > > make the most noise influence you. There will always be edge case user > > who think their needs out weight what is best for the group. > > So what you are really saying is Go to hell old farts we don't need you > here. We are not going to listen to you as you are too old to know > anything. You are old and stupid. > > It is looking like I will need to move away from FreeBSD if that is > really what is being accomplished here. Honestly. That statement irritated me, as well. Who is Ernie to act as the FreeBSD spokesman, and for what's best for FreeBSD as a whole. :( > > > > > Remember that your updated book will become a bible for many years and > > many readers. Don't include items that are now on the edge of being > > replaced. > > > > Another candidate is JAILs  IE: the old way of jail definition was in > > rc.conf the new way being jail.conf. The jail.conf method was > > introduction was at RELEASE 9.0 and here its 11.1 and still the old > > school users fight to retain both ways. Hoping that with 12.0, support > > for jail definition in rc.conf will be totally removed. > > > > One last though. The problem with the Freebsd handbook is that it reads > > like a list of reminder notes. The reader is expected to already have a > > well defined understanding of the subject being read about. The past 2 > > years a great amount of effort has gone into bring the handbook up to > > date with the current status of the operating system. But it is a very > > far cry from a teaching aid. > > > > Please take the time to rework the original "Absolute FreeBSD" content > > into something that is usable as a teaching book. You must assume that > > the only thing the reader knows about Freebsd is how to spell the word > > Freebsd and build the content from there. > > > > Good luck. > > > > > > > > > > > > > > > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 22:05:13 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2DD7E43C05 for ; Thu, 5 Oct 2017 22:05:13 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A991263717 for ; Thu, 5 Oct 2017 22:05:12 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95M5AMa063578 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 22:05:11 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> From: Grzegorz Junka Message-ID: Date: Thu, 5 Oct 2017 22:05:05 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:05:14 -0000 On 05/10/2017 21:53, Chris H wrote: > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote > >>> On 5 Oct, 2017, at 10:28, Steve Kargl >>> wrote: >>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: >>>>> On 5 Oct, 2017, at 9:25, Steve Kargl >>>>> wrote: Which brings me back to my i686 laptop with limited resources. >>>>> If portmgr makes it impractical/impossible to easily install ports >>>>> without a sledge hammer, then testing possible future patches to >>>>> libm will simply skip i686 class hardware. >>>> I'm not clear what role you think portmgr has in this. Portmgr >>>> merely brings new features to the ports tree. Portmgr itself is >>>> responsible for no build tool other than "make install". >>>> >>>> I don't know how many times I need to keep saying this, but >>>> portmgr is not killing off portmaster. There is simply nobody >>>> developing portmaster anymore, and that is not portmgr's >>>> responsibility. There ARE people developing poudriere, and >>>> that is why poudriere continues to work with new ports tree features. >>>> >>> I suppose it's a matter of semantics. If the Makefiles and *.mk >>> files under /usr/ports are altered to allow subpackages and >>> flavours to enhance pkg and poudriere, which will break portmaster >>> further, then yes portmgr has made a decision to endorse a sledge >>> hammer over simple tools. >>> >>> Mere users of the ports collection are not privy to discussions >>> on a portmgr alias/mailinglist. A quick scan of the members of >>> portmgr and contributors to poudriere show at least 4 common >>> members. There are 8 people listed under portmgr. When decisions >>> were being made on the introduction of subpackages/flavours into >>> the ports collection, did the 4 common members recluse themselves >>> from any formal or informal vote? If no, then there is certainly >>> a conflict-of-interest in what is best for the ports collection >>> versus what is best for poudriere. >>> >>> Yes, portmaster is currently unmaintained. Doug Barton left >>> FreeBSD developement because he was continually brow beaten >>> whenever he pointed out what he felt were (serious) flaws in >>> FreeBSD and in the ports collection. >> Not quite. It works in the other direction. Ports isn't designed for >> poudriere. Poudriere is designed for ports. 100% of the flavours development >> is happening in public. Anybody who wishes to work on portmaster can >> participate in the process too. >> >> I think you have a misperception of the relationship between portmgr and >> poudriere. The coming flavours would break poudriere too, except there are >> people actively developing it. >> >> You seem to be fully convinced in a conspiracy to destroy portmaster, and I >> don't get the impression that I'm going to change your mind. All I can tell >> you is that impending portmaster breakage is NOT by design, and is only >> happening because portmaster isn't actively developed anymore. If you'd like >> to believe in secret poudriere cabals and anti-portmaster conspiracies, >> that's up to you. >> >> # Adam > While I have no intention to speak on Steve's behalf. I /would/ like > to speak in his humble defense; > over year ago, I attempted to become maintainer for > ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in > it's value, and 2) it had been scorned for some time, and there were > /many/ discussions to have it removed. At the time I attempted the > request, it had not "officially" had a maintainer, and there was > serious talk as to /really/ having it removed from the ports tree. > bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the > mailing list for portmaster /will/ show /many/ heated discussions > regarding it's removal -- this thread included. In any event, after > a few inquiries regarding taking maintainer for the port. My request > was ultimately declined. I was deemed unqualified. That judgement was > unfounded. :( > Granted, maintenance of portmaster is no small feat -- it's an > enormous scriptbal. But now some months later, I am maintainer for > ~120 ports! perform a search for portmaster@ and see for yourself. > You can say what you will about some of those ports, but what it > /does/ show, is commitment, and long term commitment to boot! > I grow weary of the circular discussions surrounding portmaster. So > this is what I'd like to propose. It's maintenance is a bigger job for > anyone whom is not it's original author, for anyone that did not > grow it from scratch, and become so intimately familiar with it. So > perhaps a better solution might be for me to attempt again ask to > become maintainer. But this time, make it a group effort -- if for What does it mean in practical terms? A list of signatories under your candidature and a recommendation letter? Endorsements sent to a particular email? I don't quite understand why would anybody want to decline a request to maintain a port that is unmaintained otherwise? Are they expecting better candidatures? I would understand if they had 10 proposals to maintain the same port, but not if there is just one? But I am not good at politics so maybe I am missing something. GrzegorzJ From owner-freebsd-ports@freebsd.org Thu Oct 5 22:08:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD6FBE43CB6 for ; Thu, 5 Oct 2017 22:08:59 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A7B56381A for ; Thu, 5 Oct 2017 22:08:58 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from raspberrypi.bildanet.com ([65.186.81.207]) by cmsmtp with ESMTP id 0EK7eS9xKeXb60EK9ebfMj; Thu, 05 Oct 2017 22:08:57 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1e0EK6-0006fE-RC for freebsd-ports@freebsd.org; Thu, 05 Oct 2017 22:08:54 +0000 Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> From: Baho Utot Message-ID: Date: Thu, 5 Oct 2017 18:08:54 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfCOfiMK4kbyJIfG4cdgxZU3w59beIr30l8Ukz+fOjXEwfJDrAE66+7MyrctbIdKviOOtvJ9Fkf4xOfqyH1E+AEseTH8bvY8rlsplu7/42UdwBCSq+a+d lSVQ8niop4v6go/+SH8lSJDnOexkNQ1tiMU/ZxK1j1Vzh3rZxCHx7L7IOzfgRua1yq3y7SHgY1MlotD9+tzkO/ksCtQwKH4+8XQ= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:08:59 -0000 On 10/05/17 16:27, Grzegorz Junka wrote: > > On 05/10/2017 19:54, Baho Utot wrote: >> >> >> On 10/04/17 16:39, Ernie Luzar wrote: >> >>> Here's my take on that. >>> >>> The future direction has already been decided by the FreeBSD leaders >>> 2 years ago with their development of a better pkg system. >>> >> >> [putolin] >> >>> Don't let the few old school die hearts who are afraid of any change >>> and make the most noise influence you. There will always be edge case >>> user who think their needs out weight what is best for the group. >> >> So what you are really saying is Go to hell old farts we don't need >> you here.  We are not going to listen to you as you are too old to >> know anything.  You are old and stupid. >> >> It is looking like I will need to move away from FreeBSD if that is >> really what is being accomplished here. > > But do those old farts have anything interesting to say or they are just > making noise? What's the alternative to the proposed direction? > > GrzegorzJ Everyone should be heard. who knows if the direction would be the same? You won't hear from this old fart as every time I have had a question or input on direction All I got was grief. The last time was about pkgng. As someone that moved from LFS/building my own distribution to FreeBSD, and adding a package manager and tools for LFS. I think I may have learned something in that process. SO what did you folks do, Well I was just bitch slapped down. So much for user input. Hell pkgng can not even merge configurations file in /etc when is that going to be fixed. Also the packaging of base is just a cluster fuck, there are no other words for that non sense. When the base packaging was started it was told that by 11.0 it would be done and here it is at 11.1 and it still a cluster fuck. Now you want to add flavors, good grief you can not even finish the other projects that were started how will this flavors thing work out? Anyway it looks like I will be moving to OpenBSD or just go back to rolling my own as I have more free time to pursue building systems that work for me. FreeBSD just doesn't look like it will be a fit for me in the future. From owner-freebsd-ports@freebsd.org Thu Oct 5 22:11:41 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF5DFE43D3D for ; Thu, 5 Oct 2017 22:11:41 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCFC563AA6 for ; Thu, 5 Oct 2017 22:11:40 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95MFrYA019176 for ; Thu, 5 Oct 2017 15:15:59 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> , From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 15:15:59 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <1f06cb3836f2dd5cc3aec3e8264945ed@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:11:42 -0000 On Thu, 5 Oct 2017 20:27:19 +0000 Grzegorz Junka wrote > On 05/10/2017 19:54, Baho Utot wrote: > > > > > > On 10/04/17 16:39, Ernie Luzar wrote: > > > >> Here's my take on that. > >> > >> The future direction has already been decided by the FreeBSD leaders > >> 2 years ago with their development of a better pkg system. > >> > > > > [putolin] > > > >> Don't let the few old school die hearts who are afraid of any change > >> and make the most noise influence you. There will always be edge case > >> user who think their needs out weight what is best for the group. > > > > So what you are really saying is Go to hell old farts we don't need > > you here. We are not going to listen to you as you are too old to > > know anything. You are old and stupid. > > > > It is looking like I will need to move away from FreeBSD if that is > > really what is being accomplished here. > > But do those old farts have anything interesting to say or they are just > making noise? What's the alternative to the proposed direction?\ This is an *extremely* difficult question to answer, and these discussions come up all too often. The short answer is; shut up and code! -- Meaning; since FreeBSD exists, and grows because of those whom are willing to produce code to accomplish it. Those who put their code, where their mouth is, will be the deciding vote. :) I'm not always loving it. But it is, what it is, and it's hard to argue with it. No? :) --Chris P.S. I'm one of the "Greybeards" ;) > > GrzegorzJ > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 22:13:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54E4EE43ECA for ; Thu, 5 Oct 2017 22:13:42 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F97C63BF7 for ; Thu, 5 Oct 2017 22:13:39 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 529b0d62 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 5 Oct 2017 16:13:37 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: portmaster, portupgrade, etc From: Adam Weinberger In-Reply-To: <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> Date: Thu, 5 Oct 2017 16:13:36 -0600 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> To: Chris H X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:13:42 -0000 > On 5 Oct, 2017, at 15:53, Chris H wrote: >=20 > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger = wrote >=20 >>> On 5 Oct, 2017, at 10:28, Steve Kargl = >>> wrote:=20 >>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: >>>>> On 5 Oct, 2017, at 9:25, Steve Kargl = >>>>> wrote: Which brings me back to my i686 laptop with limited = resources. >>>>> If portmgr makes it impractical/impossible to easily install ports >>>>> without a sledge hammer, then testing possible future patches to=20= >>>>> libm will simply skip i686 class hardware. >>>>=20 >>>> I'm not clear what role you think portmgr has in this. Portmgr >>>> merely brings new features to the ports tree. Portmgr itself is >>>> responsible for no build tool other than "make install". >>>>=20 >>>> I don't know how many times I need to keep saying this, but >>>> portmgr is not killing off portmaster. There is simply nobody >>>> developing portmaster anymore, and that is not portmgr's >>>> responsibility. There ARE people developing poudriere, and >>>> that is why poudriere continues to work with new ports tree = features. >>>>=20 >>>=20 >>> I suppose it's a matter of semantics. If the Makefiles and *.mk >>> files under /usr/ports are altered to allow subpackages and >>> flavours to enhance pkg and poudriere, which will break portmaster >>> further, then yes portmgr has made a decision to endorse a sledge >>> hammer over simple tools. >>>=20 >>> Mere users of the ports collection are not privy to discussions >>> on a portmgr alias/mailinglist. A quick scan of the members of=20 >>> portmgr and contributors to poudriere show at least 4 common >>> members. There are 8 people listed under portmgr. When decisions >>> were being made on the introduction of subpackages/flavours into >>> the ports collection, did the 4 common members recluse themselves >>> from any formal or informal vote? If no, then there is certainly >>> a conflict-of-interest in what is best for the ports collection >>> versus what is best for poudriere. >>>=20 >>> Yes, portmaster is currently unmaintained. Doug Barton left >>> FreeBSD developement because he was continually brow beaten >>> whenever he pointed out what he felt were (serious) flaws in >>> FreeBSD and in the ports collection. >>=20 >> Not quite. It works in the other direction. Ports isn't designed for >> poudriere. Poudriere is designed for ports. 100% of the flavours = development >> is happening in public. Anybody who wishes to work on portmaster can >> participate in the process too.=20 >>=20 >> I think you have a misperception of the relationship between portmgr = and >> poudriere. The coming flavours would break poudriere too, except = there are >> people actively developing it.=20 >>=20 >> You seem to be fully convinced in a conspiracy to destroy portmaster, = and I >> don't get the impression that I'm going to change your mind. All I = can tell >> you is that impending portmaster breakage is NOT by design, and is = only >> happening because portmaster isn't actively developed anymore. If = you'd like >> to believe in secret poudriere cabals and anti-portmaster = conspiracies, >> that's up to you.=20 >>=20 >> # Adam > While I have no intention to speak on Steve's behalf. I /would/ like > to speak in his humble defense; > over year ago, I attempted to become maintainer for > ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in > it's value, and 2) it had been scorned for some time, and there were > /many/ discussions to have it removed. At the time I attempted the > request, it had not "officially" had a maintainer, and there was > serious talk as to /really/ having it removed from the ports tree. > bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the > mailing list for portmaster /will/ show /many/ heated discussions > regarding it's removal -- this thread included. In any event, after > a few inquiries regarding taking maintainer for the port. My request > was ultimately declined. I was deemed unqualified. That judgement was > unfounded. :( I remember that. I have to admit, I was pretty shocked by it as well. > Granted, maintenance of portmaster is no small feat -- it's an > enormous scriptbal. But now some months later, I am maintainer for > ~120 ports! perform a search for portmaster@ and see for yourself. > You can say what you will about some of those ports, but what it > /does/ show, is commitment, and long term commitment to boot! > I grow weary of the circular discussions surrounding portmaster. So > this is what I'd like to propose. It's maintenance is a bigger job for > anyone whom is not it's original author, for anyone that did not > grow it from scratch, and become so intimately familiar with it. So > perhaps a better solution might be for me to attempt again ask to > become maintainer. But this time, make it a group effort -- if for > no other reason, for my own sanity. But better; that it can/will be > more promptly addressed. IOW problems that arise, can more easily > be addressed when a group of individuals are involved with it's > maintenance. >=20 > Seem a reasonable request? If [found] so, I'll solicit for qualified > individuals to work with me on it in a new thread. >=20 > Thanks for your time, and consideration Please reach out to tz first, as he currently maintains the port. = Portmaster desperately needs an active developer, and even better if = there's a team involved (single responsibility is always a bad long-term = plan). Let me know what you need. I'll give you whatever support I can. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Oct 5 22:19:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97AACE44023 for ; Thu, 5 Oct 2017 22:19:23 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6AC1263DDB for ; Thu, 5 Oct 2017 22:19:23 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 144DAD4FF; Thu, 5 Oct 2017 15:19:16 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1507241956; bh=7j/J+zlJzjeEncAnqkNzNO2mcmZBhawm3mnoqtfnhBs=; h=Subject:To:References:From:Date:In-Reply-To; b=Omb8gJM4gJimm3EVIKZOI5uFdcsftDRkt1hVyKpfHFVrqZgVyeV91UD+J5A7YXvse TmkmPE+CiQ8h/0on+Fag7qH2VoJMzO9wi1lH/nC4JbTtdawxjGyS7RJGPT792JIn9M nn5VGGylcjTvH6l4MEU8ji9hnn7if3LJkNiu94kI= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 1AC21D4E1 for ; Thu, 5 Oct 2017 15:19:14 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1507241954; bh=7j/J+zlJzjeEncAnqkNzNO2mcmZBhawm3mnoqtfnhBs=; h=Subject:To:References:From:Date:In-Reply-To; b=aJjXMAQl3PaFa0oCP5QVPbdMkpULpm08dRpkqKIHghXKUG1J03sps6nxT8u2Q4E6C 3He4gtHDNTGKsjWQR/2KAv9iR4lcTZ5OHrQBbpUhOMUefIhNeGgRR1e90bTBpliHnH /y1tyIOM/VkRtfY6F/V7WfJnq7JCIIK4N0x/U9p0= Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> From: "Russell L. Carter" Message-ID: Date: Thu, 5 Oct 2017 15:19:13 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:19:23 -0000 On 10/05/17 14:53, Chris H wrote: > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote > >>> On 5 Oct, 2017, at 10:28, Steve Kargl >>> wrote: >>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: >>>>> On 5 Oct, 2017, at 9:25, Steve Kargl >>>>> wrote: Which brings me back to my i686 laptop with limited resources. >>>>> If portmgr makes it impractical/impossible to easily install ports >>>>> without a sledge hammer, then testing possible future patches to >>>>> libm will simply skip i686 class hardware. >>>> >>>> I'm not clear what role you think portmgr has in this. Portmgr >>>> merely brings new features to the ports tree. Portmgr itself is >>>> responsible for no build tool other than "make install". >>>> >>>> I don't know how many times I need to keep saying this, but >>>> portmgr is not killing off portmaster. There is simply nobody >>>> developing portmaster anymore, and that is not portmgr's >>>> responsibility. There ARE people developing poudriere, and >>>> that is why poudriere continues to work with new ports tree features. >>>> >>> >>> I suppose it's a matter of semantics. If the Makefiles and *.mk >>> files under /usr/ports are altered to allow subpackages and >>> flavours to enhance pkg and poudriere, which will break portmaster >>> further, then yes portmgr has made a decision to endorse a sledge >>> hammer over simple tools. >>> >>> Mere users of the ports collection are not privy to discussions >>> on a portmgr alias/mailinglist. A quick scan of the members of >>> portmgr and contributors to poudriere show at least 4 common >>> members. There are 8 people listed under portmgr. When decisions >>> were being made on the introduction of subpackages/flavours into >>> the ports collection, did the 4 common members recluse themselves >>> from any formal or informal vote? If no, then there is certainly >>> a conflict-of-interest in what is best for the ports collection >>> versus what is best for poudriere. >>> >>> Yes, portmaster is currently unmaintained. Doug Barton left >>> FreeBSD developement because he was continually brow beaten >>> whenever he pointed out what he felt were (serious) flaws in >>> FreeBSD and in the ports collection. >> >> Not quite. It works in the other direction. Ports isn't designed for >> poudriere. Poudriere is designed for ports. 100% of the flavours development >> is happening in public. Anybody who wishes to work on portmaster can >> participate in the process too. >> >> I think you have a misperception of the relationship between portmgr and >> poudriere. The coming flavours would break poudriere too, except there are >> people actively developing it. >> >> You seem to be fully convinced in a conspiracy to destroy portmaster, and I >> don't get the impression that I'm going to change your mind. All I can tell >> you is that impending portmaster breakage is NOT by design, and is only >> happening because portmaster isn't actively developed anymore. If you'd like >> to believe in secret poudriere cabals and anti-portmaster conspiracies, >> that's up to you. >> >> # Adam > While I have no intention to speak on Steve's behalf. I /would/ like > to speak in his humble defense; > over year ago, I attempted to become maintainer for > ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in > it's value, and 2) it had been scorned for some time, and there were > /many/ discussions to have it removed. At the time I attempted the > request, it had not "officially" had a maintainer, and there was > serious talk as to /really/ having it removed from the ports tree. > bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the > mailing list for portmaster /will/ show /many/ heated discussions > regarding it's removal -- this thread included. In any event, after > a few inquiries regarding taking maintainer for the port. My request > was ultimately declined. I was deemed unqualified. That judgement was > unfounded. :( > Granted, maintenance of portmaster is no small feat -- it's an > enormous scriptbal. But now some months later, I am maintainer for > ~120 ports! perform a search for portmaster@ and see for yourself. > You can say what you will about some of those ports, but what it > /does/ show, is commitment, and long term commitment to boot! > I grow weary of the circular discussions surrounding portmaster. So > this is what I'd like to propose. It's maintenance is a bigger job for > anyone whom is not it's original author, for anyone that did not > grow it from scratch, and become so intimately familiar with it. So > perhaps a better solution might be for me to attempt again ask to > become maintainer. But this time, make it a group effort -- if for > no other reason, for my own sanity. But better; that it can/will be > more promptly addressed. IOW problems that arise, can more easily > be addressed when a group of individuals are involved with it's > maintenance. > > Seem a reasonable request? If [found] so, I'll solicit for qualified > individuals to work with me on it in a new thread. > > Thanks for your time, and consideration Why don't you fork portmaster, call it eg portmaster-ch, make it a port, hack away, and see what happens. If people start using it, you win. We all win. 2¢, whatever. Russell > --Chris >> >> >> -- >> Adam Weinberger >> adamw@adamw.org >> https://www.adamw.org >> >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Thu Oct 5 22:23:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2569E441A6 for ; Thu, 5 Oct 2017 22:23:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C67D364123 for ; Thu, 5 Oct 2017 22:23:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95MRcKf020549 for ; Thu, 5 Oct 2017 15:27:44 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net>, From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 15:27:44 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:23:27 -0000 On Thu, 5 Oct 2017 22:05:05 +0000 Grzegorz Junka wrote > On 05/10/2017 21:53, Chris H wrote: > > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote > > > >>> On 5 Oct, 2017, at 10:28, Steve Kargl > >>> wrote: > >>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: > >>>>> On 5 Oct, 2017, at 9:25, Steve Kargl > >>>>> wrote: Which brings me back to my i686 laptop with limited resources. > >>>>> If portmgr makes it impractical/impossible to easily install ports > >>>>> without a sledge hammer, then testing possible future patches to > >>>>> libm will simply skip i686 class hardware. > >>>> I'm not clear what role you think portmgr has in this. Portmgr > >>>> merely brings new features to the ports tree. Portmgr itself is > >>>> responsible for no build tool other than "make install". > >>>> > >>>> I don't know how many times I need to keep saying this, but > >>>> portmgr is not killing off portmaster. There is simply nobody > >>>> developing portmaster anymore, and that is not portmgr's > >>>> responsibility. There ARE people developing poudriere, and > >>>> that is why poudriere continues to work with new ports tree features. > >>>> > >>> I suppose it's a matter of semantics. If the Makefiles and *.mk > >>> files under /usr/ports are altered to allow subpackages and > >>> flavours to enhance pkg and poudriere, which will break portmaster > >>> further, then yes portmgr has made a decision to endorse a sledge > >>> hammer over simple tools. > >>> > >>> Mere users of the ports collection are not privy to discussions > >>> on a portmgr alias/mailinglist. A quick scan of the members of > >>> portmgr and contributors to poudriere show at least 4 common > >>> members. There are 8 people listed under portmgr. When decisions > >>> were being made on the introduction of subpackages/flavours into > >>> the ports collection, did the 4 common members recluse themselves > >>> from any formal or informal vote? If no, then there is certainly > >>> a conflict-of-interest in what is best for the ports collection > >>> versus what is best for poudriere. > >>> > >>> Yes, portmaster is currently unmaintained. Doug Barton left > >>> FreeBSD developement because he was continually brow beaten > >>> whenever he pointed out what he felt were (serious) flaws in > >>> FreeBSD and in the ports collection. > >> Not quite. It works in the other direction. Ports isn't designed for > >> poudriere. Poudriere is designed for ports. 100% of the flavours > >> development is happening in public. Anybody who wishes to work on > >> portmaster can participate in the process too. > >> > >> I think you have a misperception of the relationship between portmgr and > >> poudriere. The coming flavours would break poudriere too, except there are > >> people actively developing it. > >> > >> You seem to be fully convinced in a conspiracy to destroy portmaster, and > >> I don't get the impression that I'm going to change your mind. All I can > >> tell you is that impending portmaster breakage is NOT by design, and is > >> only happening because portmaster isn't actively developed anymore. If > >> you'd like to believe in secret poudriere cabals and anti-portmaster > >> conspiracies, that's up to you. > >> > >> # Adam > > While I have no intention to speak on Steve's behalf. I /would/ like > > to speak in his humble defense; > > over year ago, I attempted to become maintainer for > > ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in > > it's value, and 2) it had been scorned for some time, and there were > > /many/ discussions to have it removed. At the time I attempted the > > request, it had not "officially" had a maintainer, and there was > > serious talk as to /really/ having it removed from the ports tree. > > bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the > > mailing list for portmaster /will/ show /many/ heated discussions > > regarding it's removal -- this thread included. In any event, after > > a few inquiries regarding taking maintainer for the port. My request > > was ultimately declined. I was deemed unqualified. That judgement was > > unfounded. :( > > Granted, maintenance of portmaster is no small feat -- it's an > > enormous scriptbal. But now some months later, I am maintainer for > > ~120 ports! perform a search for portmaster@ and see for yourself. > > You can say what you will about some of those ports, but what it > > /does/ show, is commitment, and long term commitment to boot! > > I grow weary of the circular discussions surrounding portmaster. So > > this is what I'd like to propose. It's maintenance is a bigger job for > > anyone whom is not it's original author, for anyone that did not > > grow it from scratch, and become so intimately familiar with it. So > > perhaps a better solution might be for me to attempt again ask to > > become maintainer. But this time, make it a group effort -- if for > > What does it mean in practical terms? A list of signatories under your > candidature and a recommendation letter? Endorsements sent to a > particular email? > > I don't quite understand why would anybody want to decline a request to > maintain a port that is unmaintained otherwise? Are they expecting > better candidatures? I would understand if they had 10 proposals to > maintain the same port, but not if there is just one? But I am not good > at politics so maybe I am missing something. I'm afraid I'm not really following you. What I'm saying, is that I am seeking to be Maintainer for ports-mgmt/portmaster. I am saying that it is an especially difficult task to perform -- especially in light of 1) it isn't even up-to-date for the /current/ state of the ports tree, and 2) isn't [yet] ready for Flavo[u]rs, 3) let alone sub-packages. So I would feel more inclined to make the Maintenance effort, a /team/ effort. So that those whom currently depend on it, and continue to enjoy it's use. I hope this helps clear my intentions up. :) --Chris P.S. If it's regarding the "heated discussions" regarding it's removal; simply grep the ports mailing list. In fact, here's an excerpt from the SVN commit logs: ports-mgmt/portmaster: DEPRECATE without expiration date The portmaster script hasn't had an official maintainer in 9 months and 2 years before that it was only patched in reaction to changes in the ports framework. There are many unclaimed PRs in the bugzilla database, many known bugs, and several areas where portmaster no longer aligns with how ports work today. The problem isn't simply getting a maintainer; that person has to be a ports framework expert and it appears that the people with these qualifications don't want anything to do with this port. Moreover, there are better options available. All FreeBSD platforms support ports-mgmt/poudriere (although some many struggle under the load) and the most common amd64 and i386 platform users have the additional option of ports-mgmt/synth which is user-friendly, lightweight, and aimed at users of portmaster, portupgrade, and even poudriere. Unless something drastic regarding portmaster occurs, it's nearing its natural EOL, so it's users should evaluate alternatives and try to migrate off of it. and here: Under strong objection and mandate by portmgr, remove DEPRECATION I've been ordered by portmgr to remove DEPRECATION designation because others have indicated they believe people should not be so directly informed of its poor state. Despite the fact that there was no expiration date set and that functionality was not affected in any way (leaving now informed people free to use this unmaintained port), it was considered a disruptive change. Let the record show that I strongly object to this decision and that I firmly believe that portmaster is a port that *must* have a competent maintainer that can *develop* it. It should *not* be allowed to be unmaintained and still maintain a presence in FreeBSD documentation. > > GrzegorzJ > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 22:23:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA0D1E441C8 for ; Thu, 5 Oct 2017 22:23:40 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49959641A3 for ; Thu, 5 Oct 2017 22:23:39 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95MNa05063872 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 22:23:37 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> From: Grzegorz Junka Message-ID: <8d3cda7c-2785-2bf7-a763-7f8c7e99b0a7@gjunka.com> Date: Thu, 5 Oct 2017 22:23:31 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:23:40 -0000 On 05/10/2017 22:08, Baho Utot wrote: > > > On 10/05/17 16:27, Grzegorz Junka wrote: >> >> On 05/10/2017 19:54, Baho Utot wrote: >>> >>> >>> On 10/04/17 16:39, Ernie Luzar wrote: >>> >>>> Here's my take on that. >>>> >>>> The future direction has already been decided by the FreeBSD >>>> leaders 2 years ago with their development of a better pkg system. >>>> >>> >>> [putolin] >>> >>>> Don't let the few old school die hearts who are afraid of any >>>> change and make the most noise influence you. There will always be >>>> edge case user who think their needs out weight what is best for >>>> the group. >>> >>> So what you are really saying is Go to hell old farts we don't need >>> you here. We are not going to listen to you as you are too old to >>> know anything. You are old and stupid. >>> >>> It is looking like I will need to move away from FreeBSD if that is >>> really what is being accomplished here. >> >> But do those old farts have anything interesting to say or they are >> just making noise? What's the alternative to the proposed direction? >> >> GrzegorzJ > > Everyone should be heard. who knows if the direction would be the same? > > You won't hear from this old fart as every time I have had a question > or input on direction All I got was grief. > > The last time was about pkgng. As someone that moved from > LFS/building my own distribution to FreeBSD, and adding a package > manager and tools for LFS. I think I may have learned something in > that process. SO what did you folks do, Well I was just bitch slapped > down. So much for user input. Hell pkgng can not even merge > configurations file in /etc when is that going to be fixed. Also the > packaging of base is just a cluster fuck, there are no other words for > that non sense. When the base packaging was started it was told that > by 11.0 it would be done and here it is at 11.1 and it still a cluster > fuck. Now you want to add flavors, good grief you can not even > finish the other projects that were started how will this flavors > thing work out? > > Anyway it looks like I will be moving to OpenBSD or just go back to > rolling my own as I have more free time to pursue building systems > that work for me. FreeBSD just doesn't look like it will be a fit for > me in the future. > What you are saying (or what I am reading) is that the direction isn't wrong, but rather that there is too much technical debt being left behind. That's not the same thing. Merging configurations in /etc or packaging of base are fixable regardless if there are flavours or not. So, again, what's the alternative to the proposed direction? If you are saying that there could have been a better alternative if the technical debt hasn't been left behind then I still don't get it how it would have made a difference. GrzegorzJ From owner-freebsd-ports@freebsd.org Thu Oct 5 22:32:52 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02188E44398 for ; Thu, 5 Oct 2017 22:32:52 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D50D864558 for ; Thu, 5 Oct 2017 22:32:51 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95Mb2n6021310; Thu, 5 Oct 2017 15:37:08 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Adam Weinberger Cc: In-Reply-To: <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net>, <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 15:37:08 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:32:52 -0000 On Thu, 5 Oct 2017 16:13:36 -0600 Adam Weinberger wrote > > On 5 Oct, 2017, at 15:53, Chris H wrote: > > > > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote > > > >>> On 5 Oct, 2017, at 10:28, Steve Kargl > >>> wrote: > >>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: > >>>>> On 5 Oct, 2017, at 9:25, Steve Kargl > >>>>> wrote: Which brings me back to my i686 laptop with limited resources. > >>>>> If portmgr makes it impractical/impossible to easily install ports > >>>>> without a sledge hammer, then testing possible future patches to > >>>>> libm will simply skip i686 class hardware. > >>>> > >>>> I'm not clear what role you think portmgr has in this. Portmgr > >>>> merely brings new features to the ports tree. Portmgr itself is > >>>> responsible for no build tool other than "make install". > >>>> > >>>> I don't know how many times I need to keep saying this, but > >>>> portmgr is not killing off portmaster. There is simply nobody > >>>> developing portmaster anymore, and that is not portmgr's > >>>> responsibility. There ARE people developing poudriere, and > >>>> that is why poudriere continues to work with new ports tree features. > >>>> > >>> > >>> I suppose it's a matter of semantics. If the Makefiles and *.mk > >>> files under /usr/ports are altered to allow subpackages and > >>> flavours to enhance pkg and poudriere, which will break portmaster > >>> further, then yes portmgr has made a decision to endorse a sledge > >>> hammer over simple tools. > >>> > >>> Mere users of the ports collection are not privy to discussions > >>> on a portmgr alias/mailinglist. A quick scan of the members of > >>> portmgr and contributors to poudriere show at least 4 common > >>> members. There are 8 people listed under portmgr. When decisions > >>> were being made on the introduction of subpackages/flavours into > >>> the ports collection, did the 4 common members recluse themselves > >>> from any formal or informal vote? If no, then there is certainly > >>> a conflict-of-interest in what is best for the ports collection > >>> versus what is best for poudriere. > >>> > >>> Yes, portmaster is currently unmaintained. Doug Barton left > >>> FreeBSD developement because he was continually brow beaten > >>> whenever he pointed out what he felt were (serious) flaws in > >>> FreeBSD and in the ports collection. > >> > >> Not quite. It works in the other direction. Ports isn't designed for > >> poudriere. Poudriere is designed for ports. 100% of the flavours > >> development is happening in public. Anybody who wishes to work on > >> portmaster can participate in the process too. > >> > >> I think you have a misperception of the relationship between portmgr and > >> poudriere. The coming flavours would break poudriere too, except there are > >> people actively developing it. > >> > >> You seem to be fully convinced in a conspiracy to destroy portmaster, and > >> I don't get the impression that I'm going to change your mind. All I can > >> tell you is that impending portmaster breakage is NOT by design, and is > >> only happening because portmaster isn't actively developed anymore. If > >> you'd like to believe in secret poudriere cabals and anti-portmaster > >> conspiracies, that's up to you. > >> > >> # Adam > > While I have no intention to speak on Steve's behalf. I /would/ like > > to speak in his humble defense; > > over year ago, I attempted to become maintainer for > > ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in > > it's value, and 2) it had been scorned for some time, and there were > > /many/ discussions to have it removed. At the time I attempted the > > request, it had not "officially" had a maintainer, and there was > > serious talk as to /really/ having it removed from the ports tree. > > bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the > > mailing list for portmaster /will/ show /many/ heated discussions > > regarding it's removal -- this thread included. In any event, after > > a few inquiries regarding taking maintainer for the port. My request > > was ultimately declined. I was deemed unqualified. That judgement was > > unfounded. :( > > I remember that. I have to admit, I was pretty shocked by it as well. > > > Granted, maintenance of portmaster is no small feat -- it's an > > enormous scriptbal. But now some months later, I am maintainer for > > ~120 ports! perform a search for portmaster@ and see for yourself. > > You can say what you will about some of those ports, but what it > > /does/ show, is commitment, and long term commitment to boot! > > I grow weary of the circular discussions surrounding portmaster. So > > this is what I'd like to propose. It's maintenance is a bigger job for > > anyone whom is not it's original author, for anyone that did not > > grow it from scratch, and become so intimately familiar with it. So > > perhaps a better solution might be for me to attempt again ask to > > become maintainer. But this time, make it a group effort -- if for > > no other reason, for my own sanity. But better; that it can/will be > > more promptly addressed. IOW problems that arise, can more easily > > be addressed when a group of individuals are involved with it's > > maintenance. > > > > Seem a reasonable request? If [found] so, I'll solicit for qualified > > individuals to work with me on it in a new thread. > > > > Thanks for your time, and consideration > > Please reach out to tz first, Will do. > as he currently maintains the port. Portmaster > desperately needs an active developer, and even better if there's a team > involved (single responsibility is always a bad long-term plan). > > Let me know what you need. I'll give you whatever support I can. > That's really big of you to say. Thanks Adam. You're a saint! It's going to take some planning, and organization. But I'm on it. Thanks again. > # Adam --Chris > > > -- > Adam Weinberger > adamw@adamw.org > https://www.adamw.org From owner-freebsd-ports@freebsd.org Thu Oct 5 22:33:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F72DE4440D for ; Thu, 5 Oct 2017 22:33:43 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0674E64629 for ; Thu, 5 Oct 2017 22:33:42 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95MXeiU064052 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 22:33:40 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> From: Grzegorz Junka Message-ID: <7eca64c0-7ce5-4392-a78d-d1e3b06be098@gjunka.com> Date: Thu, 5 Oct 2017 22:33:35 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:33:43 -0000 On 05/10/2017 22:27, Chris H wrote: > On Thu, 5 Oct 2017 22:05:05 +0000 Grzegorz Junka wrote > >> On 05/10/2017 21:53, Chris H wrote: >>> On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote >>> >>>>> On 5 Oct, 2017, at 10:28, Steve Kargl >>>>> wrote: >>>>> On Thu, Oct 05, 2017 at 09:31:41AM -0600, Adam Weinberger wrote: >>>>>>> On 5 Oct, 2017, at 9:25, Steve Kargl >>>>>>> wrote: Which brings me back to my i686 laptop with limited resources. >>>>>>> If portmgr makes it impractical/impossible to easily install ports >>>>>>> without a sledge hammer, then testing possible future patches to >>>>>>> libm will simply skip i686 class hardware. >>>>>> I'm not clear what role you think portmgr has in this. Portmgr >>>>>> merely brings new features to the ports tree. Portmgr itself is >>>>>> responsible for no build tool other than "make install". >>>>>> >>>>>> I don't know how many times I need to keep saying this, but >>>>>> portmgr is not killing off portmaster. There is simply nobody >>>>>> developing portmaster anymore, and that is not portmgr's >>>>>> responsibility. There ARE people developing poudriere, and >>>>>> that is why poudriere continues to work with new ports tree features. >>>>>> >>>>> I suppose it's a matter of semantics. If the Makefiles and *.mk >>>>> files under /usr/ports are altered to allow subpackages and >>>>> flavours to enhance pkg and poudriere, which will break portmaster >>>>> further, then yes portmgr has made a decision to endorse a sledge >>>>> hammer over simple tools. >>>>> >>>>> Mere users of the ports collection are not privy to discussions >>>>> on a portmgr alias/mailinglist. A quick scan of the members of >>>>> portmgr and contributors to poudriere show at least 4 common >>>>> members. There are 8 people listed under portmgr. When decisions >>>>> were being made on the introduction of subpackages/flavours into >>>>> the ports collection, did the 4 common members recluse themselves >>>>> from any formal or informal vote? If no, then there is certainly >>>>> a conflict-of-interest in what is best for the ports collection >>>>> versus what is best for poudriere. >>>>> >>>>> Yes, portmaster is currently unmaintained. Doug Barton left >>>>> FreeBSD developement because he was continually brow beaten >>>>> whenever he pointed out what he felt were (serious) flaws in >>>>> FreeBSD and in the ports collection. >>>> Not quite. It works in the other direction. Ports isn't designed for >>>> poudriere. Poudriere is designed for ports. 100% of the flavours >>>> development is happening in public. Anybody who wishes to work on >>>> portmaster can participate in the process too. >>>> >>>> I think you have a misperception of the relationship between portmgr and >>>> poudriere. The coming flavours would break poudriere too, except there are >>>> people actively developing it. >>>> >>>> You seem to be fully convinced in a conspiracy to destroy portmaster, and >>>> I don't get the impression that I'm going to change your mind. All I can >>>> tell you is that impending portmaster breakage is NOT by design, and is >>>> only happening because portmaster isn't actively developed anymore. If >>>> you'd like to believe in secret poudriere cabals and anti-portmaster >>>> conspiracies, that's up to you. >>>> >>>> # Adam >>> While I have no intention to speak on Steve's behalf. I /would/ like >>> to speak in his humble defense; >>> over year ago, I attempted to become maintainer for >>> ports-mgmt/portmaster. I did so 1) because I /strongly/ believed in >>> it's value, and 2) it had been scorned for some time, and there were >>> /many/ discussions to have it removed. At the time I attempted the >>> request, it had not "officially" had a maintainer, and there was >>> serious talk as to /really/ having it removed from the ports tree. >>> bdrewery@ had been nursing it along. Conspiracy, or not. Grepping the >>> mailing list for portmaster /will/ show /many/ heated discussions >>> regarding it's removal -- this thread included. In any event, after >>> a few inquiries regarding taking maintainer for the port. My request >>> was ultimately declined. I was deemed unqualified. That judgement was >>> unfounded. :( >>> Granted, maintenance of portmaster is no small feat -- it's an >>> enormous scriptbal. But now some months later, I am maintainer for >>> ~120 ports! perform a search for portmaster@ and see for yourself. >>> You can say what you will about some of those ports, but what it >>> /does/ show, is commitment, and long term commitment to boot! >>> I grow weary of the circular discussions surrounding portmaster. So >>> this is what I'd like to propose. It's maintenance is a bigger job for >>> anyone whom is not it's original author, for anyone that did not >>> grow it from scratch, and become so intimately familiar with it. So >>> perhaps a better solution might be for me to attempt again ask to >>> become maintainer. But this time, make it a group effort -- if for >> What does it mean in practical terms? A list of signatories under your >> candidature and a recommendation letter? Endorsements sent to a >> particular email? >> >> I don't quite understand why would anybody want to decline a request to >> maintain a port that is unmaintained otherwise? Are they expecting >> better candidatures? I would understand if they had 10 proposals to >> maintain the same port, but not if there is just one? But I am not good >> at politics so maybe I am missing something. > I'm afraid I'm not really following you. What I'm saying, is that I > am seeking to be Maintainer for ports-mgmt/portmaster. > I am saying that it is an especially difficult task to perform -- > especially in light of 1) it isn't even up-to-date for the /current/ > state of the ports tree, and 2) isn't [yet] ready for Flavo[u]rs, 3) > let alone sub-packages. So I would feel more inclined to make the > Maintenance effort, a /team/ effort. So that those whom currently > depend on it, and continue to enjoy it's use. > I hope this helps clear my intentions up. :) I do get it now, sorry for the confusion. But in that case I frankly don't think you should expect much help ;-| Developers who would be able to help you maintain the port most likely are already happily using poudriere... From owner-freebsd-ports@freebsd.org Thu Oct 5 22:59:39 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97E11E448E1 for ; Thu, 5 Oct 2017 22:59:39 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 35B1A64F79 for ; Thu, 5 Oct 2017 22:59:38 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v95MxaG2064375 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 5 Oct 2017 22:59:36 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p4FE21BFE.dip0.t-ipconnect.de [79.226.27.254] claimed to be ultrabook.yoonka.com Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> <1f06cb3836f2dd5cc3aec3e8264945ed@ultimatedns.net> From: Grzegorz Junka Message-ID: <25c2ebf5-79ab-13f2-23f2-de22aab0a6b0@gjunka.com> Date: Thu, 5 Oct 2017 22:59:31 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1f06cb3836f2dd5cc3aec3e8264945ed@ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 22:59:39 -0000 On 05/10/2017 22:15, Chris H wrote: > On Thu, 5 Oct 2017 20:27:19 +0000 Grzegorz Junka wrote > >> On 05/10/2017 19:54, Baho Utot wrote: >>> >>> On 10/04/17 16:39, Ernie Luzar wrote: >>> >>>> Here's my take on that. >>>> >>>> The future direction has already been decided by the FreeBSD leaders >>>> 2 years ago with their development of a better pkg system. >>>> >>> [putolin] >>> >>>> Don't let the few old school die hearts who are afraid of any change >>>> and make the most noise influence you. There will always be edge case >>>> user who think their needs out weight what is best for the group. >>> So what you are really saying is Go to hell old farts we don't need >>> you here. We are not going to listen to you as you are too old to >>> know anything. You are old and stupid. >>> >>> It is looking like I will need to move away from FreeBSD if that is >>> really what is being accomplished here. >> But do those old farts have anything interesting to say or they are just >> making noise? What's the alternative to the proposed direction?\ > This is an *extremely* difficult question to answer, and these discussions > come up all too often. The short answer is; shut up and code! -- Meaning; > since FreeBSD exists, and grows because of those whom are willing to > produce code to accomplish it. Those who put their code, where their > mouth is, will be the deciding vote. :) > I'm not always loving it. But it is, what it is, and it's hard to argue > with it. No? :) Yes and no. You are absolutely right that those able to code will have an advantage over those who just shout at others but do nothing, even if those who code don't do exactly what those who shout would like them to do. But that's shortsighted. There are better ways of spending time than developing something that no one else is going to use. FreeBSD exists for its users. This doesn't mean those who shout the loudest or those with esoteric needs that no one has time to cater for. This means the 90% who are not even subscribed to this list or the 99% who have never expressed their opinion about the direction FreeBSD should take either on this list or anywhere else (the silent majority). They vote for the proposed direction either by adopting FreeBSD and spreading the word around, or by abandoning it and moving to other systems without expressing any complaints. That's the reality. Now, from that perspective it doesn't really matter if portmaster is maintained or not. What does matter is if the proposed changes to pkg and the ports system are going to make the life of an average user easier or not. Everything else should be secondary. GrzegorzJ From owner-freebsd-ports@freebsd.org Thu Oct 5 23:11:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03184E44F23 for ; Thu, 5 Oct 2017 23:11:29 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4A3665BE6 for ; Thu, 5 Oct 2017 23:11:28 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v95NFeCj024944 for ; Thu, 5 Oct 2017 16:15:46 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <25c2ebf5-79ab-13f2-23f2-de22aab0a6b0@gjunka.com> References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> <1f06cb3836f2dd5cc3aec3e8264945ed@ultimatedns.net>, <25c2ebf5-79ab-13f2-23f2-de22aab0a6b0@gjunka.com> From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 16:15:46 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <55696ec41c916cd61664cd1a651fc273@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 23:11:29 -0000 On Thu, 5 Oct 2017 22:59:31 +0000 Grzegorz Junka wrote > On 05/10/2017 22:15, Chris H wrote: > > On Thu, 5 Oct 2017 20:27:19 +0000 Grzegorz Junka wrote > > > >> On 05/10/2017 19:54, Baho Utot wrote: > >>> > >>> On 10/04/17 16:39, Ernie Luzar wrote: > >>> > >>>> Here's my take on that. > >>>> > >>>> The future direction has already been decided by the FreeBSD leaders > >>>> 2 years ago with their development of a better pkg system. > >>>> > >>> [putolin] > >>> > >>>> Don't let the few old school die hearts who are afraid of any change > >>>> and make the most noise influence you. There will always be edge case > >>>> user who think their needs out weight what is best for the group. > >>> So what you are really saying is Go to hell old farts we don't need > >>> you here. We are not going to listen to you as you are too old to > >>> know anything. You are old and stupid. > >>> > >>> It is looking like I will need to move away from FreeBSD if that is > >>> really what is being accomplished here. > >> But do those old farts have anything interesting to say or they are just > >> making noise? What's the alternative to the proposed direction?\ > > This is an *extremely* difficult question to answer, and these discussions > > come up all too often. The short answer is; shut up and code! -- Meaning; > > since FreeBSD exists, and grows because of those whom are willing to > > produce code to accomplish it. Those who put their code, where their > > mouth is, will be the deciding vote. :) > > I'm not always loving it. But it is, what it is, and it's hard to argue > > with it. No? :) > > Yes and no. You are absolutely right that those able to code will have > an advantage over those who just shout at others but do nothing, even if > those who code don't do exactly what those who shout would like them to > do. But that's shortsighted. There are better ways of spending time than > developing something that no one else is going to use. > > FreeBSD exists for its users. This doesn't mean those who shout the > loudest or those with esoteric needs that no one has time to cater for. > This means the 90% who are not even subscribed to this list or the 99% > who have never expressed their opinion about the direction FreeBSD > should take either on this list or anywhere else (the silent majority). > > They vote for the proposed direction either by adopting FreeBSD and > spreading the word around, or by abandoning it and moving to other > systems without expressing any complaints. That's the reality. > > Now, from that perspective it doesn't really matter if portmaster is > maintained or not. What does matter is if the proposed changes to pkg > and the ports system are going to make the life of an average user > easier or not. Everything else should be secondary. Like I said; I'm not always loving it. and I'm not attempting to argue with you. :) But in the end. Those who put their code where their mouth is, almost always win the argument. Tho, when /enough/ non-coders speak up. That can also make a difference too. :) > > GrzegorzJ --Chris > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Oct 5 23:29:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 458E7E455DE for ; Thu, 5 Oct 2017 23:29:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1787F66423 for ; Thu, 5 Oct 2017 23:29:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 65F3420DFB for ; Thu, 5 Oct 2017 19:29:19 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 05 Oct 2017 19:29:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=t6z6lxbiVdeObBukCrR7Mw3K0KyxAa4ZlYtpNbinh HI=; b=AFAIijW//X67kvN6ZBzxnYVYqLVfbCE0r4I1NNJsO6mxmeo7s+1AxvPFJ qtlyigcspI8a36C6K+5A7luZsLLGojzIwfWI+rQs8wHJ39pyWzcO4XHynG+0PLyg Rigx+E/IqzvqKBLERE5hNuJiNhDn+S9h36luyu29yqja2ZVvaZq45pUsNuWtu4qY ldtD4Yu1Tf3tOVTIiuao5Aydy+XTvIDocw95taLCqSmqPlMzY5DbeTqtQW2260OL EkFb6aW8dNfsa6RSLAAQDs//MGvJhdgraLWKykCThWMjSkrfQy6M84be8kYARDCY zHp+5KEFNmL+uFz8ftB1/TtniARbQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=t6z6lxbiVdeObBukCr R7Mw3K0KyxAa4ZlYtpNbinhHI=; b=qixqgxt/R5wjlqguKkHFP/+M+ytKI9ErWK ZeGr3NN1dedIGb7WFuDDxFvd3bSJUPLB8cvDDX9LK76XR6QybKHosJvFHF4Fhs18 owmHiZSRB+Hx5226R097BhMTxjIYCQOSIXzbEmfgKNodK1/wgG3Uf1FPKLK96rPO WrA0HsGDpfpxDve5B7tCL6U6drYQjTiVIUjp1IU7XB4hmWsnLbigjesjH26K8+dQ V+UaO5vlr8Z2UxMQi0DKuvziTO3JiA4b5PRSB7Jm6cckiXdRng7z81sEvBebI3/I z3b+RFWwoEA0KPg9bgW9YYS+X/shld/bL++6+87TD9G+mfSFgUag== X-ME-Sender: X-Sasl-enc: FbT3gxhQeckkHyKeM2okhZQYEmKaqQlrd6ykbtXIbp4B 1507246159 Received: from v007.zyxst.net (v007.zyxst.net [89.145.100.139]) by mail.messagingengine.com (Postfix) with ESMTPA id E5D70248B1 for ; Thu, 5 Oct 2017 19:29:18 -0400 (EDT) Date: Fri, 6 Oct 2017 00:29:17 +0100 From: tech-lists To: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171005232917.GA27057@v007.zyxst.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> <1809004.bypIp25Zg3@curlew.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1809004.bypIp25Zg3@curlew.lan> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 23:29:27 -0000 On Thu, Oct 05, 2017 at 12:22:30PM +0100, Mike Clarke wrote: >the currently available package is built against php56. Using poudriere for this one task would >be equivalent to using a steamroller to crack a peanut. Building phpMyAdmin from ports is no >great problem for me and perhaps future development of pkg might avoid the need to build >my own version but I'd hope that documented methods will continue to exist for users with >this type of need. I encountered exactly this issue a few days ago. Was suprised to find that I couldn't find phpmyadmin built against php70 in packages, so built php70 then built phpmyadmin. This was easy just using the ports framework. I hope the ability to use the ports tree like this never disappears as it's one of freebsd's great strengths i think. I'd use packages more were it not for the received wisdom that mixing packages and ports is a Bad Thing (tm) - is this still the case? -- J. From owner-freebsd-ports@freebsd.org Fri Oct 6 00:00:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4E00E45E4C for ; Fri, 6 Oct 2017 00:00:31 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AD61066FE5 for ; Fri, 6 Oct 2017 00:00:31 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id v96000nS026070 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 5 Oct 2017 20:00:06 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> From: George Mitchell Message-ID: <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> Date: Thu, 5 Oct 2017 19:59:51 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qQbHCd1HG6LFmuocp9rEBOD5oC4Re4q9l" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Thu, 05 Oct 2017 20:00:11 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 00:00:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qQbHCd1HG6LFmuocp9rEBOD5oC4Re4q9l Content-Type: multipart/mixed; boundary="FkLptmAC6In6i4dU1XrAMbUdt9nQW4n7M"; protected-headers="v1" From: George Mitchell To: freebsd-ports@freebsd.org Message-ID: <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> Subject: Re: portmaster, portupgrade, etc References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> In-Reply-To: <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org> --FkLptmAC6In6i4dU1XrAMbUdt9nQW4n7M Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/05/17 18:13, Adam Weinberger wrote: >> [...] >> Seem a reasonable request? If [found] so, I'll solicit for qualified >> individuals to work with me on it in a new thread. >> >> Thanks for your time, and consideration >=20 > [...] > Let me know what you need. I'll give you whatever support I can. >=20 > # Adam >=20 >=20 I'll second that. -- George (old fart w/50 years software experience) --FkLptmAC6In6i4dU1XrAMbUdt9nQW4n7M-- --qQbHCd1HG6LFmuocp9rEBOD5oC4Re4q9l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlnWx4AACgkQwRES3m+p 4fn3+BAAtXXN1LKVHgRdpIim7n4h52Gy3v3QO0BE067SFVEgr9JNRzHecoxZ9PNx sSWOY4K2cq7ZIGl9ZA7Bh1aVy72w1o4MY4Vnspyz7ldfi+yNO8GXWWOYzyiMJkCq D02yNErr4sEf8IEqOyC//uODVPT1nhQJb9zwGHl78XU3pE9VJw42Ql7h/SyZkB1t cqAflZRXC4SS7+XK16bGUl+E3bYRiV1oOk/h3G+CAj916ZLrWjeBCaEF5HubAzRX uXXCgYSoMKC27EEqOJmJ759guOBtwUuIwEAkBvtLRKL1/kp6gPcRLHkQZUIbUXW+ tlE3i0gyUyvLjymHGYmWMfbAosfUfDs9gZkIBXMHaKApb5RRdoUlQd068uOE2kxd RgmPZSAg10rMqyvKoKbFUfPjw9W6v4ld3kuREC9xhPG7iaXCMnULHMGCo3QbFIlq DH4i2QS/UMyf3nsBBH9H+JXMbguVscDsDJL+I5yPt8YziDKheFruWKmjODTxuYaj cbYFrFB/W6FtosKbVmmZlo+IJlpPcSUu8tMcDD0INC/JEr2c9rTm/k3NO7ikqMdS I0+xlswbNCGLXYmK9cGKLZBHpLTCD/eJfoBpxIM+w+DBbLXidbqp//EpFXj3agoj cvIj06yEMHGwTmjYUKlJvd1VVqH5j6l4+BakLHegOlxcSHF4yxg= =8ZhJ -----END PGP SIGNATURE----- --qQbHCd1HG6LFmuocp9rEBOD5oC4Re4q9l-- From owner-freebsd-ports@freebsd.org Fri Oct 6 00:16:01 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4F4AE02675 for ; Fri, 6 Oct 2017 00:16:01 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ADC8D67909 for ; Fri, 6 Oct 2017 00:16:00 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v960KDcN030934; Thu, 5 Oct 2017 17:20:19 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-ports@freebsd.org, George Mitchell In-Reply-To: <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org>, <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 17:20:19 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <703eb176112501c21cdeebd23ebe066e@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 00:16:01 -0000 On Thu, 5 Oct 2017 19:59:51 -0400 George Mitchell wrote > On 10/05/17 18:13, Adam Weinberger wrote: > >> [...] > >> Seem a reasonable request? If [found] so, I'll solicit for qualified > >> individuals to work with me on it in a new thread. > >> > >> Thanks for your time, and consideration > > > > [...] > > Let me know what you need. I'll give you whatever support I can. > > > > # Adam > > > > > I'll second that. -- George (old fart w/50 years software experience) WooHoo! another greybeard! I'm at ~50yrs myself! Thanks! I'll propose the plan to Torsten, and get back to all your generous offers! --Chris From owner-freebsd-ports@freebsd.org Fri Oct 6 00:42:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19801E10058 for ; Fri, 6 Oct 2017 00:42:35 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6BB768405 for ; Fri, 6 Oct 2017 00:42:34 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v960kmcv033379 for ; Thu, 5 Oct 2017 17:46:54 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net>, <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org>, From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Thu, 05 Oct 2017 17:46:54 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <622bef4e7c4cb5a55ab128e753a0f103@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 00:42:35 -0000 On Thu, 05 Oct 2017 15:37:08 -0700 "Chris H" wrote > > > On Thu, 5 Oct 2017 10:52:51 -0600 Adam Weinberger wrote ---8<---8<--- > > > Seem a reasonable request? If [found] so, I'll solicit for qualified > > > individuals to work with me on it in a new thread. > > > > > > Thanks for your time, and consideration > > > > Please reach out to tz first, > Will do. Done! Just awaiting his reply. :) > > as he currently maintains the port. Portmaster > > # Adam > > --Chris --Chris From owner-freebsd-ports@freebsd.org Fri Oct 6 01:32:33 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80EFDE2162F for ; Fri, 6 Oct 2017 01:32:33 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msa01y.plala.or.jp (msa01.plala.or.jp [58.93.240.1]) by mx1.freebsd.org (Postfix) with ESMTP id 05A3F69D74 for ; Fri, 6 Oct 2017 01:32:32 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc02.plala.or.jp ([172.23.12.32]) by msa01y.plala.or.jp with ESMTP id <20171006013223.HNLF9031.msa01y.plala.or.jp@msc02.plala.or.jp>; Fri, 6 Oct 2017 10:32:23 +0900 Received: from localhost ([2400:7800:4d3a:6100:5e51:4fff:fe11:73f3]) by msc02.plala.or.jp with ESMTP id <20171006013223.NTZ6556.msc02.plala.or.jp@localhost>; Fri, 6 Oct 2017 10:32:23 +0900 Date: Fri, 06 Oct 2017 10:32:13 +0900 (JST) Message-Id: <20171006.103213.2218115446898027477.ish@amail.plala.or.jp> To: m.tsatsenko@gmail.com Cc: freebsd-ports@freebsd.org Subject: please add configtest command to milter-greylist From: Masachika ISHIZUKA X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; msa01m; Fri, 6 Oct 2017 10:32:23 +0900 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 01:32:33 -0000 Dear m.tsatsenko. I want to add 'configtest' extra_command to mail/milter-greylist like that. extra_commands="configtest" configtest_cmd="/usr/local/libexec/milter-greylist -c" -- Masachika ISHIZUKA From owner-freebsd-ports@freebsd.org Fri Oct 6 03:26:15 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7708E255D8 for ; Fri, 6 Oct 2017 03:26:15 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AABBD6C73A for ; Fri, 6 Oct 2017 03:26:15 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e0JHA-000EWD-FJ; Fri, 06 Oct 2017 05:26:12 +0200 Date: Fri, 6 Oct 2017 05:26:12 +0200 From: Kurt Jaeger To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006032612.GS86601@home.opsec.eu> References: <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 03:26:16 -0000 Hi! > > a few inquiries regarding taking maintainer for the port. My request > > was ultimately declined. I was deemed unqualified. That judgement was > > unfounded. :( Right now, tz@ is the maintainer of ports-mgmt/portmaster. If someone wants to become maintainer, the best way is to look at the open PRs: https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster verify their status and provide patches. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Fri Oct 6 04:31:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 533C5E26E31 for ; Fri, 6 Oct 2017 04:31:54 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 059D36DF42 for ; Fri, 6 Oct 2017 04:31:54 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-ua0-x235.google.com with SMTP id f46so10425976uae.1 for ; Thu, 05 Oct 2017 21:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6Q+LUzDvtLjcgrGY5eEwtRCNVp/ZH18HFuSFouVQpqM=; b=NCGsvfqVTivV1StA0uYjndXdINLqQeNngSLsd02Y/Wmgf44ePFJEFoja91I2NTCUMX StmcjaL3YZBLEoJQ0OtCqQIf+fQjTAfnlezyfF4q0mReIJhKqxvYEqbC1z4nI40/rEX/ 9WNF68FY8+nra3NKdNtfdlIq9pCdS/BbP5IveLuTKhCATCZvOR7YZ7A95ruxGFP4hm73 3GMttiM3bq5l+LaXoAMKaHLmxrF4/iPdtl9OcFQD6f1anevXtL5TKvuruygYQgsfJYZE vukVLD8mF3iyY52SF//In0u3FTtvlOFdv1OBOIvgVLsjSTYSBxtZvBba+jgxlxG/14HJ 8s+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6Q+LUzDvtLjcgrGY5eEwtRCNVp/ZH18HFuSFouVQpqM=; b=TTIEskYBVgcJdnVX55b2OOwqTejs3yw39lactRK67RVlfQYVnrSp0eDIfL+n2FtiG/ eYg/cPfCgltrS+1kJYXaZyx8kHsre7DVQecScClJFouBrZ8c1FBrrapttcA/vmV9ZAfj 6BsBwAg7T7iw4N50xG2eIvj738OVYu0dpQ8y1SDwnoX/mNIJZs7InTY+V6yAD3I9nQvq x/YCspR4NpCVBa6QnSBWiDSWQjayXZeQk/+8kQlZXFTMnurzNYksHMuND06FEG0H0FgR WQqXMEQSeg9MVmQqTodFDGkJHbTXxG61bJDiohrbU71JEmTBIdY4mlIO+qtycA5q9Z0J Z7mg== X-Gm-Message-State: AMCzsaVL7d6I3Cs7TOhbE/IPkwX36dBLzwUQQqlBQ3XqyniwlxP/53H5 ZUcweUhHUYNF+kedQjVzrV+YhghUNUgWkeAvrrc= X-Google-Smtp-Source: AOwi7QC9sRKhc138MTqJcBJKI9YkBD2jt4H1q6KMACevUrIQ5x1T+yLaHNqTmmPUZOVqPsctW2yoaiDfSYDtf5VKQFQ= X-Received: by 10.176.5.101 with SMTP id 92mr437086uax.188.1507264312990; Thu, 05 Oct 2017 21:31:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.21.203 with HTTP; Thu, 5 Oct 2017 21:31:52 -0700 (PDT) In-Reply-To: <20171006032612.GS86601@home.opsec.eu> References: <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <20171006032612.GS86601@home.opsec.eu> From: blubee blubeeme Date: Fri, 6 Oct 2017 12:31:52 +0800 Message-ID: Subject: Re: portmaster, portupgrade, etc To: Kurt Jaeger Cc: Grzegorz Junka , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 04:31:54 -0000 I'd vote to have Chris H be the maintainer of this port. Why knock the guy if he wants to invest his time and energy into doing something to help the project? Does it cause anyone pain to see someone working on maintaining the project? Why would someone say no you cannot maintain this port, especially when no one else is doing the work? The only best way I've ever seen to find a really good developer is find someone with dedication and willingness to take on hard challenges and stick to it. Chris seems like that type of person, who would deny the man a chance to donate his time to the FreeBSD project? Who would stand up and say, no Chris you can't maintain the port and why? On Fri, Oct 6, 2017 at 11:26 AM, Kurt Jaeger wrote: > Hi! > > > > a few inquiries regarding taking maintainer for the port. My request > > > was ultimately declined. I was deemed unqualified. That judgement was > > > unfounded. :( > > Right now, tz@ is the maintainer of ports-mgmt/portmaster. > > If someone wants to become maintainer, the best way is to > look at the open PRs: > > https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster > > verify their status and provide patches. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Fri Oct 6 04:53:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6890AE27224 for ; Fri, 6 Oct 2017 04:53:49 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1396A6E675 for ; Fri, 6 Oct 2017 04:53:49 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e0Kdu-000EcZ-Nk; Fri, 06 Oct 2017 06:53:46 +0200 Date: Fri, 6 Oct 2017 06:53:46 +0200 From: Kurt Jaeger To: blubee blubeeme Cc: FreeBSD Ports Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006045346.GT86601@home.opsec.eu> References: <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <20171006032612.GS86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 04:53:49 -0000 Hi! > I'd vote to have Chris H be the maintainer of this port. > Why knock the guy if he wants to invest his time and > energy into doing something to help the project? > Does it cause anyone pain to see someone working on > maintaining the project? Why would someone say no you cannot maintain this > port, especially when no one else is doing the work? In general, if a port has a maintainer, the idea is that that old maintainer is willing to hand over the port to the new maintainer, because the new maintainer submits more and tested patches etc. I'm not implying anything about portmaster, just stating the general idea. > Who would stand up and say, no Chris you can't maintain the port and why? Being listed or not being listed in the maintainer field of the port Makefile does not change the problem of updates/patches. Someone has to provide patches, otherwise there's no progress. Again, I'm not implying anything about portmaster, just stating the general idea. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Fri Oct 6 06:27:20 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2A47E2D9A1 for ; Fri, 6 Oct 2017 06:27:20 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 741B671064 for ; Fri, 6 Oct 2017 06:27:20 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:fdab:d6db:dfa:dae0]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 3C79F382D for ; Fri, 6 Oct 2017 06:27:17 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: portmaster, portupgrade, etc To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> <1809004.bypIp25Zg3@curlew.lan> <20171005232917.GA27057@v007.zyxst.net> From: Matthew Seaman Message-ID: <2cd0cd03-a00f-32c5-8d17-ace3069c29e9@FreeBSD.org> Date: Fri, 6 Oct 2017 07:27:04 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171005232917.GA27057@v007.zyxst.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ouo4e4mPhMnemnPdIoFF48Ps8sDSspBSn" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 06:27:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ouo4e4mPhMnemnPdIoFF48Ps8sDSspBSn Content-Type: multipart/mixed; boundary="AGq2PWfqKAfKKtgV1gBoqbpOjXvfACrXO"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <2cd0cd03-a00f-32c5-8d17-ace3069c29e9@FreeBSD.org> Subject: Re: portmaster, portupgrade, etc References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> <1809004.bypIp25Zg3@curlew.lan> <20171005232917.GA27057@v007.zyxst.net> In-Reply-To: <20171005232917.GA27057@v007.zyxst.net> --AGq2PWfqKAfKKtgV1gBoqbpOjXvfACrXO Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 06/10/2017 00:29, tech-lists wrote: > On Thu, Oct 05, 2017 at 12:22:30PM +0100, Mike Clarke wrote: >=20 >> the currently available package is built against php56. Using >> poudriere for this one task would >> be equivalent to using a steamroller to crack a peanut. Building >> phpMyAdmin from ports is no >> great problem for me and perhaps future development of pkg might avoid= >> the need to build >> my own version but I'd hope that documented methods will continue to >> exist for users with >> this type of need. > I encountered exactly this issue a few days ago. Was suprised to find > that I couldn't find phpmyadmin built against php70 in packages, so > built php70 > then built phpmyadmin. This was easy just using the ports framework. I > hope the ability to use the ports tree like this never disappears as > it's one of freebsd's great strengths i think. > I'd use packages more were it not for the received wisdom that mixing > packages and ports is a Bad Thing (tm) - is this still the case? Yes -- exactly. As maintainer of phpMyAdmin I find these sort of enquiries depressing. phpMyAdmin gets built in the project repositories with a dependency on the ports default version of PHP, but there are a substantial group of people that would like to use a different version of PHP who we cannot serve properly. This is why we need FLAVOURS in the ports -- or in this case, actually the solution would be better provided by variable dependencies. It's particularly annoying in the case of phpMyAdmin since the process of "building" the port is literally to copy the files into the staging area.= Cheers, Matthew --AGq2PWfqKAfKKtgV1gBoqbpOjXvfACrXO-- --Ouo4e4mPhMnemnPdIoFF48Ps8sDSspBSn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZ1yI/XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATeiIP/jX57SdnuwFL+ddwgyXT3i9J DoUqJA0fjTwsH8HyZm8i9GEc3WcoTsgB7mGijLKQTuLtkebF9rtaOhDyebMaeFiU ee/TjNAUCIhy2vGMCswcbPTNJANGEnX+dYrZpNh4aV2pKbnH68AO9/p3RWpzcA/q 4eKMjxR/C1mJsxaifQUtQZvytHGGBIQZM5ScxBKK+ZrQ3vDD42uzc/A0xNpKoSzq z4TyzAcRiA2c1v+nwB5CHmVRCrHa8Syip3F4AmYk/ybzZQxE3JZ0G4cABX8xqgeS S+cHcStg9GdKwjvkXF2hBKS7tIk+B59S2pge5fSfevcCepGhtU2klCR26BoEODfC F5LshINg3L2rUoQizHbeG4QXxPKfku0xWyoDB3G6qJxtJAQWsPJJD9bhxSksEwfH wYys/nEB/bKlF50gQ9D7twXnQWMTjT2OWORL41CWc/jUy3VE2cXrYcD9jLCgECSO InQ/jznw2lHY+QHpub7ixtFUAJn4Vkrzbv49wXSdPcTuyLEfNLQFOipMORWfl6f8 ZULF8d8KFxHgPHf+U6ykmzShisqvptbwmkiwLIvD6TSUQvOHtzPjOzB3RtnJJzRb Bc4e80+ZlDQ157VJVmS3QLosQ7vOVV3ASwGbCpYtqHET2cmEXQlHQEr5KYa950UD T5SSKK2pBnpT/LyJdCB8 =yMH9 -----END PGP SIGNATURE----- --Ouo4e4mPhMnemnPdIoFF48Ps8sDSspBSn-- From owner-freebsd-ports@freebsd.org Fri Oct 6 07:41:29 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87B98E2F535 for ; Fri, 6 Oct 2017 07:41:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6DA2772CB9 for ; Fri, 6 Oct 2017 07:41:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6CFF5E2F534; Fri, 6 Oct 2017 07:41:29 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CA3FE2F533 for ; Fri, 6 Oct 2017 07:41:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 459C872CB8; Fri, 6 Oct 2017 07:41:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 7964B1CC13; Fri, 6 Oct 2017 07:41:28 +0000 (UTC) Date: Fri, 6 Oct 2017 09:41:28 +0200 From: Baptiste Daroussin To: Steve Kargl Cc: "Michael W. Lucas" , ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006074128.gg76cd72u7wxybd3@ivaldir.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gkomzx476fecmm7z" Content-Disposition: inline In-Reply-To: <20171004171518.GA22519@troutmask.apl.washington.edu> User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 07:41:29 -0000 --gkomzx476fecmm7z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote: > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > >=20 > > Poudriere really needs its own small book. Yes, you can do simple > > poudriere installs, but once you start covering it properly the docs > > quickly expand. My notes alone are longer than my af3e chapter > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > > 2018). >=20 > Please include a discussion on how to use poudriere on > a system with limited resouces (e.g., 10 GB of free > diskspace and less than 1 GB free memory). I know > portmaster works well [1] within an environment with > only 4 GB free diskspace and 1 GB memory. >=20 > [1] portmaster worked well prior to portmgr's decision > to displace simple small tools in favor of a sledge > hammer. FUD.. portmgr never took any decision like this. The problem with portmaster (beside some design flows regarding the "not bu= ild in a clean room") is that it is not maintained anymore. (Note that it has n= ever been maintained by portmgr at all). What this means is, when some highly needed features such as subpackages and flavors are coming in it will just break. portmgr is taking that into accou= nt at that is one of the reason we have decided to block the adoption of flavors = for some time to give time to people to catchup and fixup the tools they do like/use (yes documentation and simple examples are coming soon(c)(tm). This not only concerns portmaster but also portupgrade, tinderbox and ANY t= hird party tools that works on the ports tree directly. Best regards, Bapt --gkomzx476fecmm7z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXM6QACgkQY4mL3PG3 Plrbcg//dFBLuKS8QE6w9v44ptpnR28pb/L7t1bPQdtrplepqQN1mJzN6T5BvvDq Py2ehAQWvVxIXy3l5tMwLQkbgJyW8ia62z/ASTq9/7yNInGpRd98YmQQdKLZ+SNs wxoN2jIEfHMeW9grI0m2RxbjL+lB2a7QUuASTG90ecodCIGjKR8SPe/cTL9xQ3XA xwOMeysM21Q/P8SD0Y8oMx6UaXLpMJK7Ir/m3/G6ylxFPwrArZkcI++pUQxp1LG0 dLNWs4/e3goJUaH9KAG8PwHMRbhd80Qwz1LAdj8ZEzJNEK0Kcf94SafZwU0m/++0 MM9BwTCqVhxwAPT2xDpFfm0dex90MhNhkK4BwZMMenkL7ikJk2NCfcO5W/v7tJab y8Kadu/3l0BlWy+RZY09SgQ//UWUqMQXFZ7i7VX7JfGA3Bj0X4wJkqsqixrztikh gh3RPXTTXNGxMV6mJaYc7r/YPHIp2DZJKPE/vJ2HUW0cKAINzJ/jgvMG/c+nC8RJ Nmt2gz7TO0doUmr4k1fyDd6+ebhtbMylxCYF2SrDZ6UjlaaTGtjF21TbbcuPuX0s gSfWGJ1zyhMHUa+qpMuR7bijw2DDJAKRFK+GBuo/JtAqtKIC2WUvjH98oNjxVfYx D8ldgeMnxJrIjZ5Wfa+65c4BZeeRyaK5pCamiPb929GSFhirFX4= =eEPc -----END PGP SIGNATURE----- --gkomzx476fecmm7z-- From owner-freebsd-ports@freebsd.org Fri Oct 6 07:56:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBF38E2F972 for ; Fri, 6 Oct 2017 07:56:31 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from viclamta17p.bpe.bigpond.com (viclamta17p.bpe.bigpond.com [203.38.21.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BA7AF7348A for ; Fri, 6 Oct 2017 07:56:28 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from smtp.telstra.com ([10.10.26.4]) by viclafep34p-svc.bpe.nexus.telstra.com.au with ESMTP id <20171006074609.WTYL13864.viclafep34p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Fri, 6 Oct 2017 18:46:09 +1100 X-RG-Spam: Unknown X-Junkmail-Premium-Raw: score=7/83, refid=2.7.2:2017.10.6.65116:17:7.944, ip=, rules=__HAS_FROM, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __IN_REP_TO, __HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __SUBJ_ALPHA_NEGATE, __NO_HTML_TAG_RAW, BODYTEXTP_SIZE_400_LESS, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_300_399, __MIME_TEXT_P1, __MIME_TEXT_ONLY, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, IN_REP_TO, MSG_THREAD, __TO_REAL_NAMES, LEGITIMATE_SIGNS, NO_URI_FOUND, NO_CTA_URI_FOUND, BODY_SIZE_1000_LESS, BODY_SIZE_2000_LESS, __MIME_TEXT_P, NO_URI_HTTPS, BODY_SIZE_7000_LESS Received: from aneurin.horsfall.org (110.141.193.233) by smtp.telstra.com (9.0.019.16-1) id 59D680360018FF7D for freebsd-ports@freebsd.org; Fri, 6 Oct 2017 18:46:08 +1100 Received: from aneurin.horsfall.org (localhost [127.0.0.1]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id v967k8K3000926 for ; Fri, 6 Oct 2017 18:46:08 +1100 (EST) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by aneurin.horsfall.org (8.15.2/8.15.2/Submit) with ESMTP id v967k8vc000923 for ; Fri, 6 Oct 2017 18:46:08 +1100 (EST) (envelope-from dave@horsfall.org) X-Authentication-Warning: aneurin.horsfall.org: dave owned process doing -bs Date: Fri, 6 Oct 2017 18:46:08 +1100 (EST) From: Dave Horsfall To: FreeBSD Ports Subject: Re: portmaster, portupgrade, etc In-Reply-To: <703eb176112501c21cdeebd23ebe066e@ultimatedns.net> Message-ID: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org>, <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> <703eb176112501c21cdeebd23ebe066e@ultimatedns.net> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) X-GPG-Public-Key: http://www.horsfall.org/gpgkey.pub X-GPG-Fingerprint: 05B4 FFBC 0218 B438 66E0 587B EF46 7357 EF5E F58B X-Home-Page: http://www.horsfall.org/ X-Witty-Saying: "chmod 666 the_mode_of_the_beast" MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 07:56:31 -0000 On Thu, 5 Oct 2017, Chris H wrote: >> I'll second that. -- George (old fart w/50 years software experience) > > WooHoo! another greybeard! I'm at ~50yrs myself! Only 47 years exp here (the last 42 with Unix). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." From owner-freebsd-ports@freebsd.org Fri Oct 6 08:05:24 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B3BBE2FDF7 for ; Fri, 6 Oct 2017 08:05:24 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EAC5473964 for ; Fri, 6 Oct 2017 08:05:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id EA330E2FDF6; Fri, 6 Oct 2017 08:05:23 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9E05E2FDF5 for ; Fri, 6 Oct 2017 08:05:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA43673963 for ; Fri, 6 Oct 2017 08:05:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v9685Nmi002292 for ; Fri, 6 Oct 2017 08:05:23 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v9685NKJ002291; Fri, 6 Oct 2017 08:05:23 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201710060805.v9685NKJ002291@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Fri, 6 Oct 2017 08:05:23 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 08:05:24 -0000 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/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/aws-sdk-cpp | 1.2.5 | 1.2.9 ------------------------------------------------+-----------------+------------ 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 Thanks. From owner-freebsd-ports@freebsd.org Fri Oct 6 08:13:44 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B650E302D1 for ; Fri, 6 Oct 2017 08:13:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 43E1E74246 for ; Fri, 6 Oct 2017 08:13:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 3FF26E302D0; Fri, 6 Oct 2017 08:13:44 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F7AAE302CF for ; Fri, 6 Oct 2017 08:13:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 228BB74245; Fri, 6 Oct 2017 08:13:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v968DgJn034336 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 6 Oct 2017 01:13:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v968DgnU034335; Fri, 6 Oct 2017 01:13:42 -0700 (PDT) (envelope-from sgk) Date: Fri, 6 Oct 2017 01:13:42 -0700 From: Steve Kargl To: Baptiste Daroussin Cc: ports@freebsd.org, "Michael W. Lucas" Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006081342.GA34314@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171006074128.gg76cd72u7wxybd3@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171006074128.gg76cd72u7wxybd3@ivaldir.net> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 08:13:44 -0000 On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote: > On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote: > > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > > > > > > Poudriere really needs its own small book. Yes, you can do simple > > > poudriere installs, but once you start covering it properly the docs > > > quickly expand. My notes alone are longer than my af3e chapter > > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in > > > 2018). > > > > Please include a discussion on how to use poudriere on > > a system with limited resouces (e.g., 10 GB of free > > diskspace and less than 1 GB free memory). I know > > portmaster works well [1] within an environment with > > only 4 GB free diskspace and 1 GB memory. > > > > [1] portmaster worked well prior to portmgr's decision > > to displace simple small tools in favor of a sledge > > hammer. > > FUD.. portmgr never took any decision like this. > The problem with portmaster (beside some design flows regarding > the "not build in a clean room") is that it is not maintained anymore. > (Note that it has never been maintained by portmgr at all). I'm well aware of Doug Barton's history with FreeBSD. You can paint it with whatever color you want. If you (and other poudriere) contributors stated that flavors/subpackages would not be supported by poudriere, would flavors/subpackages been wedged into the ports build infrastructure? -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Fri Oct 6 08:20:27 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28814E3059C for ; Fri, 6 Oct 2017 08:20:27 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 13E1C74844 for ; Fri, 6 Oct 2017 08:20:27 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 105EAE3059B; Fri, 6 Oct 2017 08:20:27 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FFDCE3059A for ; Fri, 6 Oct 2017 08:20:27 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E38FF74843; Fri, 6 Oct 2017 08:20:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 409F31DB46; Fri, 6 Oct 2017 08:20:26 +0000 (UTC) Date: Fri, 6 Oct 2017 10:20:26 +0200 From: Baptiste Daroussin To: Steve Kargl Cc: ports@freebsd.org, "Michael W. Lucas" Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006082025.msfyxzia3muf7lfp@ivaldir.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171006074128.gg76cd72u7wxybd3@ivaldir.net> <20171006081342.GA34314@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lezj6ys54hljdg7r" Content-Disposition: inline In-Reply-To: <20171006081342.GA34314@troutmask.apl.washington.edu> User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 08:20:27 -0000 --lezj6ys54hljdg7r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 06, 2017 at 08:13:42AM +0000, Steve Kargl wrote: > On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote: > > On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote: > > > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > > > >=20 > > > > Poudriere really needs its own small book. Yes, you can do simple > > > > poudriere installs, but once you start covering it properly the docs > > > > quickly expand. My notes alone are longer than my af3e chapter > > > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" = in > > > > 2018). > > >=20 > > > Please include a discussion on how to use poudriere on > > > a system with limited resouces (e.g., 10 GB of free > > > diskspace and less than 1 GB free memory). I know > > > portmaster works well [1] within an environment with > > > only 4 GB free diskspace and 1 GB memory. > > >=20 > > > [1] portmaster worked well prior to portmgr's decision > > > to displace simple small tools in favor of a sledge > > > hammer. > >=20 > > FUD.. portmgr never took any decision like this. > > The problem with portmaster (beside some design flows regarding > > the "not build in a clean room") is that it is not maintained anymore. > > (Note that it has never been maintained by portmgr at all). >=20 > I'm well aware of Doug Barton's history with FreeBSD. You > can paint it with whatever color you want. >=20 > If you (and other poudriere) contributors stated that flavors/subpackages > would not be supported by poudriere, would flavors/subpackages been > wedged into the ports build infrastructure? Yes because if you look at mailing lists etc, you ould have figured out that this is the number one feature requested in the ports tree for years. Also yes we would have make sure that the tools used to build official pack= ages would have worked with it, prior poudriere it was tinderbox. And again we are giving time (and warning in advance) for all the tools to = catch up! Best regards, Bapt --lezj6ys54hljdg7r Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXPMcACgkQY4mL3PG3 PlrIuw//UU7kYiZJCO1WkYvyK4ULSWyTL+alGIHzEumds2p8kqWrbNgGJk0qFIbk ZW0UwHoHqK9bJGF7VdmbCUsHtb6JhipJH/8L8X/XXIfDJqX0xUXCClVcPENJOf4/ KzhmAQfSB83SWPML9urFUZ0cxmVJ7p3VuQVRANZblRoejtDkNf6wrnHRQqROjv0E Cf9a61/flfboEXbtEmjTKpsxiGdyKTdl8ySpIkx57vxN/MgVUFl9pDpvSPd+vKBI UEzqQS9LWxYD/oHpVsxnfSI7GgOMLarsIIOMbcK6DSh1DBvFGDK93KNDO9xzkepx UUPkJOjMs6WDGHEBS+05oL8BzkOyf9ULcRLdYGwos4LDZOZKpC1NqX7e+JnwGFe/ kDVuxZ1uFxUkEl5qwaXy+zntgNbhg+c/o1xv3s/qGLeiuw9Lo80q5Ulxryd8kWLq j4C+0B2Io9vHqvM6VTQQM6uECbAcG4D7vre1QI9Po668g1N1x8lAF3dZlu26EaUN LGUSNq29IlHcHzdE9ITamC+YSwXB7Cdc6XdUicUr6+AAHawtvgqgwRtYu9QNNbv2 M9PGCHjGRn/UZfYxC/sJz/ishkQF2uxSWjgVkLz0e+YUpLnst8hyP22H/6OjPeMC 86gO0ObzDkvPBzCphXMrm48MnrKQum9uQKafNWUARsaoikc0PkM= =ElS0 -----END PGP SIGNATURE----- --lezj6ys54hljdg7r-- From owner-freebsd-ports@freebsd.org Fri Oct 6 08:48:40 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DDADE30E14 for ; Fri, 6 Oct 2017 08:48:40 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from outmx-028.london.gridhost.co.uk (outmx-028.london.gridhost.co.uk [95.142.156.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 006BB75832 for ; Fri, 6 Oct 2017 08:48:39 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk (unknown [82.71.56.121]) (Authenticated sender: mailpool@milibyte.co.uk) by outmx-028.london.gridhost.co.uk (Postfix) with ESMTPA id A819521EF686D for ; Fri, 6 Oct 2017 09:41:46 +0100 (BST) Received: from [192.168.1.13] (helo=milibyte.co.uk) by curlew.milibyte.co.uk with esmtp (Exim 4.89) (envelope-from ) id 1e0OJ8-0000od-4g for freebsd-ports@freebsd.org; Fri, 06 Oct 2017 09:48:36 +0100 From: Mike Clarke To: freebsd-ports@freebsd.org Date: Fri, 06 Oct 2017 09:47:30 +0100 Message-ID: <1728350.hoGohsj294@curlew.lan> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <20171005232917.GA27057@v007.zyxst.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <1809004.bypIp25Zg3@curlew.lan> <20171005232917.GA27057@v007.zyxst.net> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: portmaster, portupgrade, etc X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 08:48:40 -0000 On Friday 06 Oct 2017 00:29:17 tech-lists wrote: > I'd use packages more were it not for the received wisdom that mixing > packages and ports is a Bad Thing (tm) - is this still the case? The main thing is to keep your ports tree synchronised with the version used for the package repository. I find that the script at https://gist.github.com/reedacartwright/8622973baf89b263a6d7 is a useful tool for this. The script hasn't been updated beyond 10.x-RELEASE so if you're running 11.x- RELEASE you need to patch the script by adding the following line: 110amd64-default) PKG_SERVER=beefy9.nyi.freebsd.org ;; If only pkg could be made to report the revision number of the ports tree it was built from we wouldn't need to hunt around for this information. -- Mike Clarke From owner-freebsd-ports@freebsd.org Fri Oct 6 08:55:14 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79135E31152 for ; Fri, 6 Oct 2017 08:55:14 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B9FF75D60; Fri, 6 Oct 2017 08:55:14 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 8EEE71E4A8; Fri, 6 Oct 2017 08:55:13 +0000 (UTC) Date: Fri, 6 Oct 2017 10:55:13 +0200 From: Baptiste Daroussin To: Baho Utot Cc: freebsd-ports@freebsd.org Subject: Re: portmaster, portupgrade, etc Message-ID: <20171006085513.73ru7knzaxzpfryi@ivaldir.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <59D546FD.30906@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="y4kt6u6gycsujlmu" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 08:55:14 -0000 --y4kt6u6gycsujlmu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 05, 2017 at 10:08:54PM +0000, Baho Utot wrote: >=20 >=20 > On 10/05/17 16:27, Grzegorz Junka wrote: > >=20 > > On 05/10/2017 19:54, Baho Utot wrote: > > >=20 > > >=20 > > > On 10/04/17 16:39, Ernie Luzar wrote: > > >=20 > > > > Here's my take on that. > > > >=20 > > > > The future direction has already been decided by the FreeBSD > > > > leaders 2 years ago with their development of a better pkg > > > > system. > > > >=20 > > >=20 > > > [putolin] > > >=20 > > > > Don't let the few old school die hearts who are afraid of any > > > > change and make the most noise influence you. There will always > > > > be edge case user who think their needs out weight what is best > > > > for the group. > > >=20 > > > So what you are really saying is Go to hell old farts we don't need > > > you here.=A0 We are not going to listen to you as you are too old to > > > know anything.=A0 You are old and stupid. > > >=20 > > > It is looking like I will need to move away from FreeBSD if that is > > > really what is being accomplished here. > >=20 > > But do those old farts have anything interesting to say or they are just > > making noise? What's the alternative to the proposed direction? > >=20 > > GrzegorzJ >=20 > Everyone should be heard. who knows if the direction would be the same? >=20 > You won't hear from this old fart as every time I have had a question or > input on direction All I got was grief. >=20 > The last time was about pkgng. As someone that moved from LFS/building my > own distribution to FreeBSD, and adding a package manager and tools for L= FS. > I think I may have learned something in that process. SO what did you fo= lks > do, Well I was just bitch slapped down. So much for user input. Hell pk= gng > can not even merge configurations file in /etc when is that going to be > fixed. It can... and for a while, the fact it is not used in packaging base is ano= ther subject, but the tool can definitly do it. [...] >=20 > Anyway it looks like I will be moving to OpenBSD or just go back to rolli= ng > my own as I have more free time to pursue building systems that work for = me. > FreeBSD just doesn't look like it will be a fit for me in the future. Have you figured out that OpenBSD is a step further in the direction you are rejecting: They have FLAVORS for decades and they do strongly recommend use= rs to use binary packages in the first place... Just sating... Bapt --y4kt6u6gycsujlmu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXROwACgkQY4mL3PG3 PlodWQ//U9WMFjuMBXLDvZ6PyqI9IC9dsoFoXa5D1zrK5aFag7/KdSFoAkx+Qyr0 MgCCg5fBLqQyfBFmISfHBP4C1+Nt5ZsvYWbI5R3ay7zC2WAblYKh71tR+l2S6X/D O+zz+3md9IdqwkdW7+GIV5zZvGHObdBDepe80I1xuq8twru61AiidPJbi7uVZc7H tYXHH5caMUtmxmyAi8Enhi+sx3Ykim69IN2LfEHqcFMIJm5LRpZltV/4Wq0/LHWX f4rzMyeghf0luYZJT9pzSHcrnifmQXVzA97HYycErnNuwGfFkWrRn0MoLItcyVAJ E5Zaa6D1PwGANcjK61stSYulGujVPwPi7H5861lgnOkrVQLzJteK7ziBUNbbkKHv imby73Pv3rW/o1A7A14eaLUulZ6faMJPEWMLSBXkfS86Am1hRZBgEfj2a2cNaJd0 7ziw+fvc1PG1yKZjMjrY8QzzUtx0ZE+Bc7mnWuwnXqK0GnOtvbKfOrZGAj/4Vydo FvGcVyvVliDjatQQqZIZ1rvVaVhbcSW+ytecFdM8B7/MwMQcZBOrOPqYPWCdkMLy Edb9Nb9qTbic2ShfJUtbUq3KiCjNUvUlddYBhFJDV8CoxrN8is1Q6hQzD9kQ2bn8 TLh8ppn/USDHD+zU/+rXfoY5H/A7EaTLlfBmU7wC8afhiJKMBOc= =2wzL -----END PGP SIGNATURE----- --y4kt6u6gycsujlmu-- From owner-freebsd-ports@freebsd.org Fri Oct 6 09:23:42 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CF95E31AB7 for ; Fri, 6 Oct 2017 09:23:42 +0000 (UTC) (envelope-from 535ca599.AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZ@bnc3.mailjet.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F30AB76CA9 for ; Fri, 6 Oct 2017 09:23:41 +0000 (UTC) (envelope-from 535ca599.AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZ@bnc3.mailjet.com) Received: by mailman.ysv.freebsd.org (Postfix) id F23E2E31AB6; Fri, 6 Oct 2017 09:23:41 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1CFBE31AB5 for ; Fri, 6 Oct 2017 09:23:41 +0000 (UTC) (envelope-from 535ca599.AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZ@bnc3.mailjet.com) Received: from o221.p13.mailjet.com (o221.p13.mailjet.com [87.253.238.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A00DE76CA8 for ; Fri, 6 Oct 2017 09:23:40 +0000 (UTC) (envelope-from 535ca599.AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZ@bnc3.mailjet.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; q=dns/txt; d=propertynewsletter2017.com; i=martin@propertynewsletter2017.com; s=mailjet; h=domainkey-signature:message-id:mime-version:from:to:subject:date:list-id:list-unsubscribe: precedence:x-csa-complaints:x-mj-mid:content-type; bh=RVa+ekUpF4hcMMcbM0OJ2tyZpkSJaOgWwKMZeu7ZItk=; b=nZ0iFHkOz8e02S9ezP+10/zaIjPCy0daB5rjGhKjaozZcBRLxuesZ2oij r1iBI/2nVIoEFH6LjB/q+jqkkezOw3C6FVUaFQib76K0yqwkxQEMTNlWkB8i d9nonYgkykvsJZ3vyjTnlk4Z9873BOhmjOz0jTnCf618uhD4EPYDko= DomainKey-Signature: a=rsa-sha1; c=simple; q=dns; d=propertynewsletter2017.com; s=mailjet; h=message-id:mime-version:from:to:subject:date:list-id:list-unsubscribe: precedence:x-csa-complaints:x-mj-mid:content-type; b=iE3csFl+tXlgfSk86OFhEbhqyKo4FjM8T8InLjx2ZqASLz8KfDGx1iCqh 61TA1rcMv5tPKZsPzijwr9Kh7D9SkyruLIRBUmBYVeg8HZNdLgjXW4SGg6w0 dGsoAm4jcJulm4yXX+3Enaxh3CtnESwOn0DYXfjNNaOtor058B61Ug= Message-Id: <535ca599.AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZ@mailjet.com> MIME-Version: 1.0 From: KLCC - Property Newsletter To: ports@freebsd.org Subject: First Kempinski 5-star hotel branded residences to launch in Asia from S$7xx,000 onwards. Date: Fri, 6 Oct 2017 09:23:37 +0000 Precedence: bulk X-CSA-Complaints: whitelist-complaints@eco.de X-MJ-Mid: AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZpmhfvmVZQFWW5nyE_EY2FAAGxrU Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 09:23:42 -0000 View online version [http://g2wq.mjt.lu/nl2/g2wq/188pn.html?m=3DAEsAAIEtmPc= AAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZpmhfvmVZQFWW5nyE_EY2FAAGxrU&b=3D53= 5ca599&e=3D7a88ef2c&x=3DG0wm0OECQNb2ARwor9YImfylvSQCW2xWeZVI4sBQ4eU] [http://bit.ly/2wzcGXD] <> [http://bit.ly/2wzcGXD] <> [http://bit.ly/2wzcGXD] <> [[[UNSUB_LINK_EN]]] DISCLAIMER Property Newsletter ("PN") is operated by GlobalCollectionSingapore ("GCS")= , a Singaporean=C2=A0 registered company that operates various business uni= ts, brands and associated Intellectual Property under license. These brands= include but are not limited to BBI or Property Newsletter (PN). You are re= ceiving this email as you have previously registered with one of the BBI bu= siness units or associates. PN offers marketing services to 3rdparty ("Advertiser(s)") and does not tak= e any responsibility for the legality or accuracy of any information provid= ed by such Advertisers. The information contained in this message is provid= ed by an Advertiser who is aware of the target audience and fully responsib= le for the legality and accuracy of the content provided, no such informati= on forms part of any contract. Although every attempt is made to work only = with ethical and professional Advertisers PN is unable to verify the conten= ts and any claims made. PN including all its directors and staff cannot be = deemed legally liable for any harm or loss incurred from the use of any inf= ormation obtained from any of its websites (including PN) or advertising me= ssages such as this. The information supplied by Advertisers is made available within messages l= ike these and, where applicable, on the=C2=A0PN web site solely for the pur= pose of providing PN subscribers, clients, suppliers and the general public= an informative portal and information relevant to their interests. PN offers links to thirdparty websites. PN does not claim to promote the co= ntents of the information contained in these websites nor does PN accept an= y responsibility for any harm or loss caused by the usage of any informatio= n contained within these websites or any other website that is linked to th= e PN or BBI=C2=A0 website. PN observes data protection law and confirms that any personal information = supplied will only be used for the purpose for which it was supplied and un= der the terms and conditions agreed to by the data supplier. Under no circu= mstances will the any personal information be passed to a thirdparty, we re= gard yourprivacy as paramount and can ensure all information will remainpri= vate. PN reserves the right to amend the content of this web site at any time wit= hout notice. This web site is a constantly evolving promotional tool, thus = changes and alterations of all kinds will happen on a regular basis. All forms of investment carry risks, including the risk of losing all the i= nvested amount. Such activities is not suitable for everyone. As overseasin= vestments carry additional financial, regulatory and legal risk, investors = are advised to do the necessary checks and research on the investment befor= ehand. Past performance not necessarily indicative of future performance. T= &C applies. This e-mail has been sent to ports@freebsd.org, click here to unsubscribe [= [[UNSUB_LINK_EN]]]. MBFC Tower 3 018974 Singapore SG= From owner-freebsd-ports@freebsd.org Fri Oct 6 12:42:06 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 343E4E365CB for ; Fri, 6 Oct 2017 12:42:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDC8981D9D for ; Fri, 6 Oct 2017 12:42:05 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v96Cfxew095192 for ; Fri, 6 Oct 2017 12:41:59 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v96CfxtM095191 for freebsd-ports@freebsd.org; Fri, 6 Oct 2017 05:41:59 -0700 (PDT) (envelope-from david) Date: Fri, 6 Oct 2017 05:41:59 -0700 From: David Wolfskill To: freebsd-ports@freebsd.org Subject: graphics/netpbm update to netpbm-10.80.00 Message-ID: <20171006124159.GJ1222@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TEnxaPCmSubUceV2" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 12:42:06 -0000 --TEnxaPCmSubUceV2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Empirical observation: environments that currently have an older installation of graphics/netpbm already installed, and where the intent is to update graphics/netpbm to netpbm-10.80.00 by building the port in the environment with the older netpbm already installed (e.g., make, portmaster, and portupgrade -- not within a jail or a chroot) may benefit from deleting the old installed version before attempting the in-place update. Disclaimer: That's what worked for me, using portmaster. In a couple of days, I expect to be updating at least one system from custom-built packages (built using poudriere); I expect that this will Just Work (without the evasive maneuver of a preemptive "pkg delete -f graphics/netpbm"). And there's another system I expect to update that same day -- rather isolated from everything else -- where I expect to use portmaster, and will need to perform said preemptive evasive maneuver. I mention it in the hope that the information will reduce the time spent trying to figure this out: time is not one of the "more renewable resources" we have. Peace, david --=20 David H. Wolfskill david@catwhisker.org http://www.cbc.ca/news/opinion/donald-trump-playbook-1.4265374 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --TEnxaPCmSubUceV2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZ13oXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XlHMIALZCJocgUL/cLUmMSmoUATtV szJjCQYJbpA84YJEL+1gBMdyqB/rZdAJx+4n3bdl/h/FWT7LEfMHccAFZ2OuZxiJ 1k6jsuWqCr31oB6WCXI0G7KOhmisJhYBMH6gjFd/1GtrT13vXsSnuzrNBgnAVEO2 Pfh5x6wzybqm6IaV4rzp2aNj9rUM0v8cXNd1XBPpW8e2y5OLqa4dVycA51RlZKzx DVqV0SJJeB182dUxexIeeSBK3JO91nL50wLZFc+C162dz7PLbE3OabcwRFzURMAr bmqxY35m4c0jhMAaZQPzPx5oVkCyK11PzQ8W9KRSNVIAVNZhVvFWlOaRjg3lnXo= =NTeE -----END PGP SIGNATURE----- --TEnxaPCmSubUceV2-- From owner-freebsd-ports@freebsd.org Fri Oct 6 13:11:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA969E36E78 for ; Fri, 6 Oct 2017 13:11:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B5E7782ADA for ; Fri, 6 Oct 2017 13:11:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B4C0AE36E77; Fri, 6 Oct 2017 13:11:47 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4565E36E76 for ; Fri, 6 Oct 2017 13:11:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94ACB82AD9 for ; Fri, 6 Oct 2017 13:11:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id C87A22455; Fri, 6 Oct 2017 13:11:46 +0000 (UTC) Date: Fri, 6 Oct 2017 15:11:46 +0200 From: Baptiste Daroussin To: ports@FreeBSD.org Subject: [RFC] less patches: control the PATH Message-ID: <20171006131146.qswg2barkhelii4n@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p4jg2himzpv3wah7" Content-Disposition: inline User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 13:11:47 -0000 --p4jg2himzpv3wah7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, Here is a patch to add a new feature I am willing to get for a while: https://reviews.freebsd.org/D12603 What this patch does it basically prepend to PATH a new directory (inside WRKDIR) A user can control which binary will be found in the PATH of the build sequences easily by adding BINARY_RENAME= source target This will create a sumlink in the WRKDIR/.bin directory: ${WRKDIR}/.bin/target -> source The goal here to avoid patching a port which needs to use for example gsed instead of our bsd sed BINARY_RENAMe= gsed sed of specify gcc will be gcc7, etc This should remove lots of custom patches in the ports tree. PS: this should break no port building tool :) PS2: the BINARY_RENAME variable name sucks, any better name is welcome :) Best regards, Bapt --p4jg2himzpv3wah7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXgRAACgkQY4mL3PG3 PlogdxAAsar4fY9T7EYR+iPpCSarXKmPy36/nz+LXSfxEXe3Oa0ekrjq79vfyEQe LQOcshlPLjoc4/cVw+SnirS+TOl7CjoFd5pw0tqz6M4DQ94hSgInENc4b6QHG5ZC K8EsEo5MBm+WnHlpvgXnlK0b2dzZio7Jn7C22tFgezvWIMGihrfT1zNYhS9GAFz1 q1OfkUSlzsegnrmTKOhrQYep7xUrjt0NYtxopLXctfsW8SZ8Gr4DtfbU3U3JP41S FNy+zQGrAiX7W0/mGpLgI1r90janx8EkljQRgadlgu/+x9lUpgAPaztVUzUEaXd+ Bz91bGWy36FjieBNMuVYlnFuIDsY5AxTcxMoChOPrTbeNIRAnVkiFXrds9WaQDnP 97pdJnaEhecqyG8xBk7hAf1ZaPVNpDRdDcc+Cuyv7gStYxgXhbGIsLYXOq//DuWP S659/k65OXaeL+9IIRhZq1wPw3jMQAk/rVcOXDpapOqMVtKgeR0dFrdeO1p6NYcD lzzpFsGK22YDFwd/BwL+UGLVi7Xls+GvRGbzp3ffSLWOlOXIXgI37s89VSDTUsW+ HrugJdKJGC9CTSjCvBHgZUiwaL6r0bX7el8ahqCSbshl3ypebEU2GonABaEMylRO lK3v0uiJ6/JAR/WbBMae03yQoJZdbJJgr+DD84odNmr1+4M/wcQ= =jvf1 -----END PGP SIGNATURE----- --p4jg2himzpv3wah7-- From owner-freebsd-ports@freebsd.org Fri Oct 6 13:23:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF766E3728F for ; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CC5A0832D8 for ; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CBAB5E3728E; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB449E3728D for ; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACC4B832D7 for ; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 0C6872779; Fri, 6 Oct 2017 13:23:50 +0000 (UTC) Date: Fri, 6 Oct 2017 15:23:49 +0200 From: Baptiste Daroussin To: ports@FreeBSD.org Subject: Re: [RFC] less patches: control the PATH Message-ID: <20171006132349.24bcqfmepwykerac@ivaldir.net> References: <20171006131146.qswg2barkhelii4n@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dp4urggl6pvcm5xj" Content-Disposition: inline In-Reply-To: <20171006131146.qswg2barkhelii4n@ivaldir.net> User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 13:23:51 -0000 --dp4urggl6pvcm5xj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 06, 2017 at 01:11:46PM +0000, Baptiste Daroussin wrote: > Hi all, >=20 > Here is a patch to add a new feature I am willing to get for a while: > https://reviews.freebsd.org/D12603 >=20 > What this patch does it basically prepend to PATH a new directory (inside > WRKDIR) >=20 > A user can control which binary will be found in the PATH of the build se= quences > easily by adding > BINARY_RENAME=3D source target >=20 > This will create a sumlink in the WRKDIR/.bin directory: > ${WRKDIR}/.bin/target -> source >=20 > The goal here to avoid patching a port which needs to use for example gsed > instead of our bsd sed > BINARY_RENAMe=3D gsed sed >=20 > of specify gcc will be gcc7, etc >=20 > This should remove lots of custom patches in the ports tree. >=20 > PS: this should break no port building tool :) > PS2: the BINARY_RENAME variable name sucks, any better name is welcome :) renamed BINARY_LINKS which is less worse :) Best regards, Bapt --dp4urggl6pvcm5xj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXg+MACgkQY4mL3PG3 PlqhehAAhqTZ8dpRW/euZyRCV61jzM9TIpbUy6VhhasQoRz0HH126bJnXHPPQkdf wH3D5yJPs6UtFuqBPtKH1pVVO+psnzXwKLF+mFDTuWhFiFpJJXsFM5r4/uJeeC4C j17tLIFn2G82Dz9RFJYrjOP8tQQNW52BW06bESx4n6WZdx+SCeiR2yiCdSrotUgz z+lq5HR3NKLlF35aBDyH5e+S7Cb3fiJyCoA9XC9P4xAlPMBtTjCkdxmU54tFqgUL 1fU++i5nZ5iIkO70zCiuOH2CLwF/unxSTbf+qWxzA6WTy40vaEekCWUIyU9tNmHV c0E70IWKxUP3AuCGiyIUOx+kaiqMS/Xzc6N/+LBnuN8a9lwlZuYLqPGlYdcdWzcr 5BsrmMG3YL5po0+iBGgkwILP80GKThPOaO/KLc2MtiK95yDBrYpp9jzMbVYfruV9 z6rvTp5bbOG+aDclqVp0Q/KFp32B5ZngqcUMjRN7BpTL87VSSyDHQeuGTuLxkWtC EYQP6XL7rOIVBJdlfUtZYpxkb5hpQDVZyTDA1wBAR538y8f+3sKNDQx73CRvWXTV nTa4+BPD0S2x4OwljzQd40vdqXbolBnY+ovUdFBaxSsampRuR0sgH67pwVtqqeaa n+wv0BDO2vCN84NJkyalfFJp6i8q60eL3Vfhu9sHmm5ILUtGNBk= =mi1r -----END PGP SIGNATURE----- --dp4urggl6pvcm5xj-- From owner-freebsd-ports@freebsd.org Fri Oct 6 13:24:16 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D164E372E9 for ; Fri, 6 Oct 2017 13:24:16 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 127DA83384 for ; Fri, 6 Oct 2017 13:24:16 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by mailman.ysv.freebsd.org (Postfix) id 0EA0DE372E7; Fri, 6 Oct 2017 13:24:16 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E4DBE372E6 for ; Fri, 6 Oct 2017 13:24:16 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42D2F8337F; Fri, 6 Oct 2017 13:24:15 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3y7r2H3yjGzZr2; Fri, 6 Oct 2017 15:24:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=mail; t=1507296245; x=1509110646; bh=/RSSi2WxRdFmhB mFR6mhN/ikY033PQ+FRWjC9bC2BK0=; b=cxEg2kGEh2pHVdG1eOkFpNSsO7OI83 6+IXlL0a1l2GoQAdsm1E0hjiTiD6/TMSEKL4Yn+e201N3r9ykJuHs9LrDwPkqvlB Nt1gXA5de6IcYLsVx7XI5dzUH9KA8WvGvwUA1ODbduzPaT6tptNnf2Io1X6GJsfw NuOX+ks/jt8do= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 3DnHv-dtGOGF; Fri, 6 Oct 2017 15:24:05 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Fri, 6 Oct 2017 15:24:05 +0200 (CEST) Subject: Re: [RFC] less patches: control the PATH To: Baptiste Daroussin , ports@FreeBSD.org References: <20171006131146.qswg2barkhelii4n@ivaldir.net> From: Guido Falsi Message-ID: <42d09435-072d-d196-1822-bb5c603b49af@madpilot.net> Date: Fri, 6 Oct 2017 15:24:04 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171006131146.qswg2barkhelii4n@ivaldir.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 13:24:16 -0000 On 10/06/2017 15:11, Baptiste Daroussin wrote: > Hi all, > > Here is a patch to add a new feature I am willing to get for a while: > https://reviews.freebsd.org/D12603 > A user can control which binary will be found in the PATH of the build sequences > easily by adding > BINARY_RENAME= source target > PS2: the BINARY_RENAME variable name sucks, any better name is welcome :) > Suggestions from the top of my head: BINARY_ALIAS PROGRAM_ALIAS EXECUTABLE_ALIAS COMMAND_ALIAS (Yes I think "alias" expresses the concept better) -- Guido Falsi From owner-freebsd-ports@freebsd.org Fri Oct 6 13:29:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDD86E3756B for ; Fri, 6 Oct 2017 13:29:26 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 871B183709 for ; Fri, 6 Oct 2017 13:29:26 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id v96DT51R030978 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 6 Oct 2017 09:29:11 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Getting off topic (Re: portmaster, portupgrade, etc) To: freebsd-ports@freebsd.org References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171006074128.gg76cd72u7wxybd3@ivaldir.net> <20171006081342.GA34314@troutmask.apl.washington.edu> <20171006082025.msfyxzia3muf7lfp@ivaldir.net> From: George Mitchell Message-ID: <674d9501-6093-166f-bcf2-b4ac9ba87d06@m5p.com> Date: Fri, 6 Oct 2017 09:28:59 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171006082025.msfyxzia3muf7lfp@ivaldir.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="r1rsAu0254DCmTAFb6nfuCiKCnCb8WxWe" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Fri, 06 Oct 2017 09:29:11 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 13:29:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --r1rsAu0254DCmTAFb6nfuCiKCnCb8WxWe Content-Type: multipart/mixed; boundary="sBdOXL0TAaIjLD4sUDvO5CBxHNNCWGjQX"; protected-headers="v1" From: George Mitchell To: freebsd-ports@freebsd.org Message-ID: <674d9501-6093-166f-bcf2-b4ac9ba87d06@m5p.com> Subject: Getting off topic (Re: portmaster, portupgrade, etc) References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171006074128.gg76cd72u7wxybd3@ivaldir.net> <20171006081342.GA34314@troutmask.apl.washington.edu> <20171006082025.msfyxzia3muf7lfp@ivaldir.net> In-Reply-To: <20171006082025.msfyxzia3muf7lfp@ivaldir.net> --sBdOXL0TAaIjLD4sUDvO5CBxHNNCWGjQX Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/06/17 04:20, Baptiste Daroussin wrote: > On Fri, Oct 06, 2017 at 08:13:42AM +0000, Steve Kargl wrote: >> On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote: >>> On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote: >>>> On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: >>>>> >>>>> Poudriere really needs its own small book. Yes, you can do simple >>>>> poudriere installs, but once you start covering it properly the doc= s >>>>> quickly expand. My notes alone are longer than my af3e chapter >>>>> limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" = in >>>>> 2018). >>>> >>>> Please include a discussion on how to use poudriere on >>>> a system with limited resouces (e.g., 10 GB of free >>>> diskspace and less than 1 GB free memory). I know >>>> portmaster works well [1] within an environment with >>>> only 4 GB free diskspace and 1 GB memory. >>>> >>>> [1] portmaster worked well prior to portmgr's decision >>>> to displace simple small tools in favor of a sledge >>>> hammer. >>> >>> FUD.. portmgr never took any decision like this. >>> The problem with portmaster (beside some design flows regarding >>> the "not build in a clean room") is that it is not maintained anymore= =2E >>> (Note that it has never been maintained by portmgr at all). >> >> I'm well aware of Doug Barton's history with FreeBSD. You >> can paint it with whatever color you want. >> >> If you (and other poudriere) contributors stated that flavors/subpacka= ges >> would not be supported by poudriere, would flavors/subpackages been >> wedged into the ports build infrastructure? >=20 > Yes because if you look at mailing lists etc, you ould have figured out= that > this is the number one feature requested in the ports tree for years. >=20 > Also yes we would have make sure that the tools used to build official = packages > would have worked with it, prior poudriere it was tinderbox. >=20 > And again we are giving time (and warning in advance) for all the tools= to catch > up! >=20 > Best regards, > Bapt >=20 Speaking solely for myself, I am more than pleased by all the work Baptiste and fellow developers have put into the ports infrastructure. THANK YOU! But also, portmaster is a life saver for me with my 4GB build machine, so I hope I can participate in reviving it. -- George --sBdOXL0TAaIjLD4sUDvO5CBxHNNCWGjQX-- --r1rsAu0254DCmTAFb6nfuCiKCnCb8WxWe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlnXhSEACgkQwRES3m+p 4floEw/+NS8gpxk8AApE4AXjgYihF6U+AKTi9xXjwgONdpbxZChoUcZUafQYAlj4 rIBeURg+XmfkULM9kjarcwOZf9X5Ri1GRRersAVdy2+Tg8wN0AayH0nsmJUDuuSM j+hxaKWhO6fGXZTvpffd6enW/u6o5d5dV/RwGjQqjtJbI5TuzJizn4hpVUH0IpJ7 v49q3R8aCOzFz80+DQh2u8DC/NxBPLlfcmFZYiOyhjC3zt9BtfzRyBgjpnt5klqh blyBa3L+igLIY3fqCqL6VoUD8jGGkqi8gsl0hIppxUC2v5I72dMrhwhWX/ZW8SRw IIdOD3E56oDfk+ddszSNw4ltjmmRGKrGqgIGwSIJ7RiMxhaJRRHIGiEvCkPy015K Y3rkSg77/1l/OFyLSAxnpvxvhcFWJ+LPB/BpzQoxY3cHFYuNjBcLE/V2MIHThdQJ 7Be/6EIAys4SrWhxJApc6J5p7hANy5narYnx3zM3wVlrW/qR13XsSycWh1p1Gx0l Gw6qwxevc10r1G3LPqwebSWwVimQb44NtZd/FGh15NnnsGxXapfAZm+XeScV6X6x Lf8F/w3G68AP0Jh0puGfGJ17G+jz6u3U3DkBgXu4zMpEhC0sEPtcsjW5+cjEiskw HRI7365DX891grrNeazxra6xnlCqeSwQ/HP32UjTdV/piyd7eBs= =R78R -----END PGP SIGNATURE----- --r1rsAu0254DCmTAFb6nfuCiKCnCb8WxWe-- From owner-freebsd-ports@freebsd.org Fri Oct 6 13:34:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FCB4E379BE for ; Fri, 6 Oct 2017 13:34:59 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 180D383B63; Fri, 6 Oct 2017 13:34:59 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 693232AE8; Fri, 6 Oct 2017 13:34:58 +0000 (UTC) Date: Fri, 6 Oct 2017 15:34:58 +0200 From: Baptiste Daroussin To: George Mitchell Cc: freebsd-ports@freebsd.org Subject: Re: Getting off topic (Re: portmaster, portupgrade, etc) Message-ID: <20171006133458.p4neunzmu3mqypa2@ivaldir.net> References: <20171004161649.GA51883@mail.michaelwlucas.com> <20171004171518.GA22519@troutmask.apl.washington.edu> <20171006074128.gg76cd72u7wxybd3@ivaldir.net> <20171006081342.GA34314@troutmask.apl.washington.edu> <20171006082025.msfyxzia3muf7lfp@ivaldir.net> <674d9501-6093-166f-bcf2-b4ac9ba87d06@m5p.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="frvciogcklecn536" Content-Disposition: inline In-Reply-To: <674d9501-6093-166f-bcf2-b4ac9ba87d06@m5p.com> User-Agent: NeoMutt/20170912 (1.9.0) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 13:34:59 -0000 --frvciogcklecn536 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 06, 2017 at 01:28:59PM +0000, George Mitchell wrote: > On 10/06/17 04:20, Baptiste Daroussin wrote: > > On Fri, Oct 06, 2017 at 08:13:42AM +0000, Steve Kargl wrote: > >> On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote: > >>> On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote: > >>>> On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote: > >>>>> > >>>>> Poudriere really needs its own small book. Yes, you can do simple > >>>>> poudriere installs, but once you start covering it properly the docs > >>>>> quickly expand. My notes alone are longer than my af3e chapter > >>>>> limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" = in > >>>>> 2018). > >>>> > >>>> Please include a discussion on how to use poudriere on > >>>> a system with limited resouces (e.g., 10 GB of free > >>>> diskspace and less than 1 GB free memory). I know > >>>> portmaster works well [1] within an environment with > >>>> only 4 GB free diskspace and 1 GB memory. > >>>> > >>>> [1] portmaster worked well prior to portmgr's decision > >>>> to displace simple small tools in favor of a sledge > >>>> hammer. > >>> > >>> FUD.. portmgr never took any decision like this. > >>> The problem with portmaster (beside some design flows regarding > >>> the "not build in a clean room") is that it is not maintained anymore. > >>> (Note that it has never been maintained by portmgr at all). > >> > >> I'm well aware of Doug Barton's history with FreeBSD. You > >> can paint it with whatever color you want. > >> > >> If you (and other poudriere) contributors stated that flavors/subpacka= ges > >> would not be supported by poudriere, would flavors/subpackages been > >> wedged into the ports build infrastructure? > >=20 > > Yes because if you look at mailing lists etc, you ould have figured out= that > > this is the number one feature requested in the ports tree for years. > >=20 > > Also yes we would have make sure that the tools used to build official = packages > > would have worked with it, prior poudriere it was tinderbox. > >=20 > > And again we are giving time (and warning in advance) for all the tools= to catch > > up! > >=20 > > Best regards, > > Bapt > >=20 > Speaking solely for myself, I am more than pleased by all the work > Baptiste and fellow developers have put into the ports infrastructure. > THANK YOU! But also, portmaster is a life saver for me with my 4GB > build machine, so I hope I can participate in reviving it. -- George >=20 Thank you, I will be more than happy to merge patches in https://github.com/freebsd/portmaster which makes it handle flavors Best regards, Bapt --frvciogcklecn536 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlnXhn8ACgkQY4mL3PG3 PloUExAAgd50F3l5wNPqCoVus37VWM0FYA3z22Hd3ke/VLz3r8VbSXJ/pcHYN5Vi k6gLrTp4P7QcNOQ/6LAZKfLk11qgb9AAHyEZBWTjPqrob8dnL0ppSQfnXUzSHGyV FVlp7zncvoxESugt4lvGV59of8zENQ5kV/Y4pWAbxymDeUcrINxXrVVql3w/SqT2 K7hbSKwQmNqnD4/GxWWq3o/IkhsJTtnNXKcE4HXig+rmQeIP8qaec1GvCK2PFqRH OPVH+U3s8S+QkJ8CkiWXVsO5OgleoIwX5t19UdzYJjlbH72eVqXnwNYuHCNz6ZBy dbaEQlUUYxG8aL/+mqf8RtyUI9IiALxiaPb+Koau+t5C2oHjl7rIUXxboPTizCVK 1FcymnNrJriJb7FmgAM8RUtCuRAK1sggIhzIL6qTe6mvm34UFTUv9+8DQkFh29cr SDcnswGhQrEYIji+cXK9y0l+nNyAtRJjzH2HLYUP8NXyi5VQ8siBwQyftQ3/Ft/y CfiO4n/9mt/bTwPVTb/lnUflyA5JoAK9i4wzAJpmN+zBFg6///BkSz86Cb2KqY1X ZHb6EKt/DPz3ELWBmiZrGlF0wB5GcsMCJ6HFIshUHRS6v9SI+mhPjG1zrC66IqQM XozVLrbpj27BjQbMHDeuGytK62Z8j2QtR3/N2cnLepduEsaQWUM= =QPTP -----END PGP SIGNATURE----- --frvciogcklecn536-- From owner-freebsd-ports@freebsd.org Fri Oct 6 14:29:30 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D554E389BA for ; Fri, 6 Oct 2017 14:29:30 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id ED34E1CFC for ; Fri, 6 Oct 2017 14:29:29 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id E96C9E389B8; Fri, 6 Oct 2017 14:29:29 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E74E8E389B7 for ; Fri, 6 Oct 2017 14:29:29 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-qt0-f194.google.com (mail-qt0-f194.google.com [209.85.216.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 664091CF9; Fri, 6 Oct 2017 14:29:29 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-qt0-f194.google.com with SMTP id p15so4853524qtp.2; Fri, 06 Oct 2017 07:29:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FRzUYhjN+VTLuZd5jYXqhBGN7dDOejH1iZlx6FyIPTc=; b=XHOM2gvX4GN1jzRSGC6bsk0o9I9j2ci9h5a1iTAfkaq3kgAo6k4wsD/ebwXAEFgFJT IATAGCmG5FNEs2FpNK5kwikapqpUnjgiErEhzqA7huXVp23dKm7gCWHhG/QBYQlLb9Jf mkowNb5mgUbCVLIkKuJt8piWLFvNGxV1GCAyclEpSahOME8FodkGl8i7im8VriZfccvM pM3Pc8TaA9jv+9bFZK0MbFTlBIWGysnbR2G4ndqc4AM6ceBt+jco6hHUGGKXckMjMi7g k73i6VWB4JUlHHMghxr0h232ZZLvvrbB3yJtd8VM2CCBMeZCPckaW+Z8o+d0Os3plc27 SLaw== X-Gm-Message-State: AMCzsaUpeJCwD7wHxYojPt2YYt1AH4IkMo76nt96zjScqU6mXIchY/5E ipL6p80AdWJ4zmDVNlJFEFAmhAnt X-Received: by 10.37.210.19 with SMTP id j19mr1587528ybg.476.1507296468385; Fri, 06 Oct 2017 06:27:48 -0700 (PDT) Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com. [209.85.218.54]) by smtp.gmail.com with ESMTPSA id c11sm498879ywb.89.2017.10.06.06.27.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2017 06:27:47 -0700 (PDT) Received: by mail-oi0-f54.google.com with SMTP id j126so29620223oia.10; Fri, 06 Oct 2017 06:27:47 -0700 (PDT) X-Google-Smtp-Source: AOwi7QDIGT4N/hTPlJjG4n2bof4faogCFs/HOHHe1eVjvKChGT3z1HHNyeNSgSCQRiz4AXBA4QNOVvgUrxH3yj/n3xY= X-Received: by 10.202.8.79 with SMTP id 76mr914034oii.199.1507296467317; Fri, 06 Oct 2017 06:27:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.36.144 with HTTP; Fri, 6 Oct 2017 06:27:46 -0700 (PDT) Received: by 10.58.36.144 with HTTP; Fri, 6 Oct 2017 06:27:46 -0700 (PDT) In-Reply-To: <42d09435-072d-d196-1822-bb5c603b49af@madpilot.net> References: <20171006131146.qswg2barkhelii4n@ivaldir.net> <42d09435-072d-d196-1822-bb5c603b49af@madpilot.net> From: Kyle Evans Date: Fri, 6 Oct 2017 08:27:46 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC] less patches: control the PATH To: Guido Falsi Cc: Baptiste Daroussin , ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 14:29:30 -0000 On Oct 6, 2017 8:24 AM, "Guido Falsi" wrote: On 10/06/2017 15:11, Baptiste Daroussin wrote: > Hi all, > > Here is a patch to add a new feature I am willing to get for a while: > https://reviews.freebsd.org/D12603 > A user can control which binary will be found in the PATH of the build sequences > easily by adding > BINARY_RENAME= source target > PS2: the BINARY_RENAME variable name sucks, any better name is welcome :) > Suggestions from the top of my head: BINARY_ALIAS PROGRAM_ALIAS EXECUTABLE_ALIAS COMMAND_ALIAS (Yes I think "alias" expresses the concept better) -- Guido Falsi +1 for BINARY_ALIAS; concise, descriptive, and accurate From owner-freebsd-ports@freebsd.org Fri Oct 6 18:55:59 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DC15E3EB32 for ; Fri, 6 Oct 2017 18:55:59 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E02496B1C9 for ; Fri, 6 Oct 2017 18:55:58 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v96J0Eop054068 for ; Fri, 6 Oct 2017 12:00:20 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <20171004232819.GA86102@troutmask.apl.washington.edu> <201710050027.v950RBFT047711@gw.catspoiler.org> <20171005083558.GD95911@kib.kiev.ua> <20171005145116.GA96180@troutmask.apl.washington.edu> <20171005145941.GL95911@kib.kiev.ua> <20171005152520.GA96545@troutmask.apl.washington.edu> <9B1E1C51-7D87-4DBC-8E7A-D9657BBAAC91@adamw.org> <20171005162853.GA96784@troutmask.apl.washington.edu> <2a1d1356e707b94e2dafa331c69ef692@ultimatedns.net> <8F813EC0-BEC2-42F1-AFA3-257569692DA8@adamw.org>, <30bb261f-5ae1-30bf-41d6-2ab6992ccb80@m5p.com> <703eb176112501c21cdeebd23ebe066e@ultimatedns.net>, From: "Chris H" Subject: Re: portmaster, portupgrade, etc Date: Fri, 06 Oct 2017 12:00:20 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <47d2d30b536ff9ea98cc0cf9424a82a4@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 18:55:59 -0000 On Fri, 6 Oct 2017 18:46:08 +1100 (EST) Dave Horsfall wrote > On Thu, 5 Oct 2017, Chris H wrote: > > >> I'll second that. -- George (old fart w/50 years software experience) > > > > WooHoo! another greybeard! I'm at ~50yrs myself! > > Only 47 years exp here (the last 42 with Unix). ..and Unix *exists* because of some whom are now "old farts" || "greybeards"! :) --Chris > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will > suffer." _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Fri Oct 6 19:39:06 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCBB7E3FF2B for ; Fri, 6 Oct 2017 19:39:06 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B1B96D144 for ; Fri, 6 Oct 2017 19:39:05 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v96Jd3xt087441 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 6 Oct 2017 19:39:03 GMT (envelope-from list1@gjunka.com) To: freebsd-ports@freebsd.org From: Grzegorz Junka Subject: Crashing chromium/iridium Message-ID: Date: Fri, 6 Oct 2017 19:39:03 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 19:39:06 -0000 Just wanted to check if anybody else observed this annoying behaviour in Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab hangs loading for 30-60 seconds, after which time the browser shows a dialog that the webpage doesn't load and I can either kill or wait. There is no pattern, sometimes I can open 10 tabs with no issues, but sometimes 10 tabs hang in a row and need to be killed. Very often when I kill the page reloading the page doesn't help, it still hangs, but when I open the same URL in a new tab it works. Sometimes, however, reloading the page also works. I compiled and installed Iridium hoping that it will be free from this bug but it seems that the behaviour is exactly the same as in Chromium. It has been happening for the past year at least. Maybe some of the options I checked for Chromium/Iridium don't work well or maybe some of its dependencies are compiled with options that don't work well. How would I investigate it? I didn't try to install precompiled versions. Also, the issue doesn't happen with other browsers (Firefox, any other I could compile on FreeBSD are also fine). I tried to open in safe mode, without extensions, but all without any difference in this behaviour. Thanks GrzegorzJ From owner-freebsd-ports@freebsd.org Fri Oct 6 19:40:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AE26E40086 for ; Fri, 6 Oct 2017 19:40:46 +0000 (UTC) (envelope-from domagoj.stolfa@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEC7C6D2EB for ; Fri, 6 Oct 2017 19:40:45 +0000 (UTC) (envelope-from domagoj.stolfa@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id i124so9864395wmf.3 for ; Fri, 06 Oct 2017 12:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RGlYXVcdvsbWhoYC77ivxC9bG9WZcJK1d6VLwN4Zbzo=; b=C4na8fTTWfnVHVssT+dXU828cpKOX1JJN4wD7BiX3oHkUmLcOI2JmiuJy+PKKr21mP Shus1AN/5C7wLu2uM6cHOGnE7LRh4w8eqkr4zixuwYMAi9rTHDPZEfm1KzHFTiqbyaSU t+XVT1Q3Xh2PpTyuSqvox5+udXWze6nf7l02jfHEyZP2L2SRer2OdDK0lxhix7oJ3l0B KMynPfGm4xo8Kn5JvdtMQzUnSmjwihAS8CWXCWYaWdK6iC1squEGEEtpPJoxB8G3090J s1h4l0KLKN1xeunwPlqfKzMWUOgjaZ0Bk2FHkv7cN0SfZqBd2h94W2P2gzcwwbVTUfLt zU/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RGlYXVcdvsbWhoYC77ivxC9bG9WZcJK1d6VLwN4Zbzo=; b=r4BtUai/v48c7GRDCrPz4pV4eXsir1i8HIA+IwBByDvJ7F9mlLUJfVKRqyPIJlFnE+ YiD+zREn6Fv7v75wQ4WGKYphj6IibpSQi0kdZFtPD8IeqzziV+HUjqrvBixdem0ne1ez TNc/fsRxFrTObqukjbgmFVZfz2eseA7q9VjWsILe+9bzp1J24YOqS6zO0yYjQGkCiU68 jyyVLyw07zYGBX9BG4DS3LDAxNgOAdwPxoCIGGnFzXsSMFQ68S0mYL+4tR1+MRN/2NrM 6BEE6tG3X9wpzbzpjXsWpqg8DKyRw8bA1iTKd/nohl4mG1HqDcXTvsqc2yGZvloyUtPO aNdQ== X-Gm-Message-State: AMCzsaXk23E1TIu3091+fVNE/knVaWUIDzbzg7tSq8DUv5TmxbqIH2Tn +TsXeNKD7LR1pwBAWThVAoM= X-Google-Smtp-Source: AOwi7QBqQrhq3dbgUk6AbwK1unffxgykp/7BLJ5J6F0a2QVbiLpR3BOlPW2A8fxVJW8ZSR/BDckTNQ== X-Received: by 10.223.135.143 with SMTP id b15mr3360952wrb.24.1507318844127; Fri, 06 Oct 2017 12:40:44 -0700 (PDT) Received: from dhcp-10-248-10-243.eduroam.wireless.private.cam.ac.uk (global-5-130.nat-2.net.cam.ac.uk. [131.111.5.130]) by smtp.gmail.com with ESMTPSA id f84sm848662wme.44.2017.10.06.12.40.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2017 12:40:43 -0700 (PDT) From: Domagoj Stolfa Message-Id: <031E224F-E158-48DD-B259-B5A746315D89@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_4B4FCCFF-A17C-41D8-A9F4-4DDE8940C5ED"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Crashing chromium/iridium Date: Fri, 6 Oct 2017 20:40:42 +0100 In-Reply-To: Cc: freebsd-ports@freebsd.org To: Grzegorz Junka References: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 19:40:46 -0000 --Apple-Mail=_4B4FCCFF-A17C-41D8-A9F4-4DDE8940C5ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99ve found this to be an issue as well. None of the things that = I=E2=80=99ve seen suggested online could fix it, and unfortunately do = not have time to look at it myself. I=E2=80=99d be interested to hear if = anyone has any more details regarding this issue. =E2=80=94 Domagoj > On 6 Oct 2017, at 20:39, Grzegorz Junka wrote: >=20 > Just wanted to check if anybody else observed this annoying behaviour = in Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the = new tab hangs loading for 30-60 seconds, after which time the browser = shows a dialog that the webpage doesn't load and I can either kill or = wait. >=20 > There is no pattern, sometimes I can open 10 tabs with no issues, but = sometimes 10 tabs hang in a row and need to be killed. Very often when I = kill the page reloading the page doesn't help, it still hangs, but when = I open the same URL in a new tab it works. Sometimes, however, reloading = the page also works. >=20 > I compiled and installed Iridium hoping that it will be free from this = bug but it seems that the behaviour is exactly the same as in Chromium. = It has been happening for the past year at least. Maybe some of the = options I checked for Chromium/Iridium don't work well or maybe some of = its dependencies are compiled with options that don't work well. How = would I investigate it? >=20 > I didn't try to install precompiled versions. Also, the issue doesn't = happen with other browsers (Firefox, any other I could compile on = FreeBSD are also fine). I tried to open in safe mode, without = extensions, but all without any difference in this behaviour. >=20 > Thanks >=20 > GrzegorzJ >=20 >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to = "freebsd-ports-unsubscribe@freebsd.org" --Apple-Mail=_4B4FCCFF-A17C-41D8-A9F4-4DDE8940C5ED Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE37fRcHC0Iwiz+ZVEg+gksMBgNd0FAlnX3DoACgkQg+gksMBg Nd2OVg//YCh+/Iu5dnV5+qKtbclTk5qFyZYCTjwdb1lPg3EIb8KrYOg1lg+IPP7z +sxOBMqkSM4Z86xsdLT4p4H1Rj+dyKB9Xr8KvADUc0LHFsDsNbHQB0pQ1WmUt5Pi BXtf1mof9eVO2TJ5yjiQ820qI864ebC24oee8H6iSsqvkJ8CLGJxWx/kd0sIfJUO JCwK44zzpkfL4ld3eqsHPvSarWaio50wnb95OIe2mfNdoDdDBnsGrDki/Kx/saks MCBpltR4mjn/yUiU8JganG+LhZf+cC7p4Y4x2EsBys+xvLWcuFofDHKa/bZGWD2I ZMdsFjpjjh3Mne3JDzeOC7z8L8ULLC97nW4sKLE4YKhJfsYJqgulYCrEegsSzDdx laSxtG/YYRKbYMnYmDs0Ca9IxjWB0OGQF71Haej2Aua6AhidsWAoAtudqX3zlL0N KtawRPiMAp9WJbelUnzifHH5Vo767aOPdz6NxMOFqZWUf4Ku7m1MGtofLUGCXYGs yR3eoBGZXelHf8D12lJxO67E27rW9/7kntyO3fpLEtn8KOBztorYOZo3Cq6uaE6C LmQPB/D1h2awe9Bxegnuy6Qf+bQBdPyWn2ZLPWlv7YzVTcNNEd7/c2ivttU41dBl DtILwgxNtPNAd9//sfKMaJmPN0LIGHioNqqIYtOQQC0k1/Dswf0= =7VO/ -----END PGP SIGNATURE----- --Apple-Mail=_4B4FCCFF-A17C-41D8-A9F4-4DDE8940C5ED-- From owner-freebsd-ports@freebsd.org Fri Oct 6 19:47:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 499BDE4035D for ; Fri, 6 Oct 2017 19:47:56 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-qt0-f171.google.com (mail-qt0-f171.google.com [209.85.216.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09AC86D78E for ; Fri, 6 Oct 2017 19:47:55 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-qt0-f171.google.com with SMTP id v28so24626946qtv.1 for ; Fri, 06 Oct 2017 12:47:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cpPSh/lGPjVR8FebpwZA61DKcdww8mRn3wQn0MRBkwg=; b=Ag294oeO78ym8oqqWHm+rvR3UtETmyScUNg+e7SxZuvV0rbMzwDUmegahlu3vhjVy5 J2HVGL1ig4X51kuA4kVoEGAvHtXl3VenYqclStUt7cWfhOMkknsSePDehTWhvHxiDL4t 9uCfqIOC94TVyIcOlxruyv0BY+OvNKOOz5MLIRb3CJ9uNAAUqN0FanNPqkSgllso0QRF ShVItZMe8TEMnHz1s6SAeuWrUJXy73whY/XaAwPX0oLjBVkKw8HYWbj5jWGaUp0JW0tM AJEQgHOfxIgiLl4seLQ4xpoTnmiduvswXdWcQGszjQeUY6rcLoTwmHxyTXwfUJ+yk/SZ Wgmg== X-Gm-Message-State: AMCzsaWmqf30wO9b1ieP6BLjmjihHFe51jxElxKqyV+XAS3rpFWqaMLa z3YpgX6QjrvdUQ/JCPDJPsSWxrCE X-Received: by 10.37.172.217 with SMTP id x25mr2475615ybd.343.1507319268509; Fri, 06 Oct 2017 12:47:48 -0700 (PDT) Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com. [209.85.218.47]) by smtp.gmail.com with ESMTPSA id a6sm2157629ywe.47.2017.10.06.12.47.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2017 12:47:47 -0700 (PDT) Received: by mail-oi0-f47.google.com with SMTP id v9so19103885oif.13 for ; Fri, 06 Oct 2017 12:47:47 -0700 (PDT) X-Google-Smtp-Source: AOwi7QCC0fkKy5oFV7jBIvf3P3QRUIw+HfF/TfpTaVf5ZKoeAG5oOqnot76CamN/+kR5SdrERSfCXnQIyxd3COTYAf4= X-Received: by 10.157.11.18 with SMTP id a18mr1733706ota.141.1507319267490; Fri, 06 Oct 2017 12:47:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.36.144 with HTTP; Fri, 6 Oct 2017 12:47:27 -0700 (PDT) In-Reply-To: <031E224F-E158-48DD-B259-B5A746315D89@gmail.com> References: <031E224F-E158-48DD-B259-B5A746315D89@gmail.com> From: Kyle Evans Date: Fri, 6 Oct 2017 14:47:27 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Crashing chromium/iridium To: Domagoj Stolfa Cc: Grzegorz Junka , ports-list freebsd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 19:47:56 -0000 For reference: there's been some escalation of this by asmodai@ (I think -- don't quote me on this): https://bugs.chromium.org/p/chromium/issues/detail= ? id=3D729534 -- asmodai@ was requesting some help in further debugging, but unfortunately does not seem to have received any help in that regard. On Fri, Oct 6, 2017 at 2:40 PM, Domagoj Stolfa wrote: > I=E2=80=99ve found this to be an issue as well. None of the things that I= =E2=80=99ve seen > suggested online could fix it, and unfortunately do not have time to look > at it myself. I=E2=80=99d be interested to hear if anyone has any more de= tails > regarding this issue. > > =E2=80=94 > Domagoj > > > On 6 Oct 2017, at 20:39, Grzegorz Junka wrote: > > > > Just wanted to check if anybody else observed this annoying behaviour i= n > Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new ta= b > hangs loading for 30-60 seconds, after which time the browser shows a > dialog that the webpage doesn't load and I can either kill or wait. > > > > There is no pattern, sometimes I can open 10 tabs with no issues, but > sometimes 10 tabs hang in a row and need to be killed. Very often when I > kill the page reloading the page doesn't help, it still hangs, but when I > open the same URL in a new tab it works. Sometimes, however, reloading th= e > page also works. > > > > I compiled and installed Iridium hoping that it will be free from this > bug but it seems that the behaviour is exactly the same as in Chromium. I= t > has been happening for the past year at least. Maybe some of the options = I > checked for Chromium/Iridium don't work well or maybe some of its > dependencies are compiled with options that don't work well. How would I > investigate it? > > > > I didn't try to install precompiled versions. Also, the issue doesn't > happen with other browsers (Firefox, any other I could compile on FreeBSD > are also fine). I tried to open in safe mode, without extensions, but all > without any difference in this behaviour. > > > > Thanks > > > > GrzegorzJ > From owner-freebsd-ports@freebsd.org Fri Oct 6 19:57:03 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23D3EE4060E for ; Fri, 6 Oct 2017 19:57:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04C276DBA7 for ; Fri, 6 Oct 2017 19:57:02 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v96K1IJB063845 for ; Fri, 6 Oct 2017 13:01:24 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <42d09435-072d-d196-1822-bb5c603b49af@madpilot.net> References: <20171006131146.qswg2barkhelii4n@ivaldir.net>, <42d09435-072d-d196-1822-bb5c603b49af@madpilot.net> From: "Chris H" Subject: Re: [RFC] less patches: control the PATH Date: Fri, 06 Oct 2017 13:01:24 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8dbf23b2be5840966f7e67f86971ecbd@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 19:57:03 -0000 On Fri, 6 Oct 2017 15:24:04 +0200 Guido Falsi wrote > On 10/06/2017 15:11, Baptiste Daroussin wrote: > > Hi all, > > > > Here is a patch to add a new feature I am willing to get for a while: > > https://reviews.freebsd.org/D12603 > > > A user can control which binary will be found in the PATH of the build > > sequences easily by adding > > BINARY_RENAME= source target > > > PS2: the BINARY_RENAME variable name sucks, any better name is welcome :) > > > > Suggestions from the top of my head: > > BINARY_ALIAS > > PROGRAM_ALIAS > > EXECUTABLE_ALIAS > > COMMAND_ALIAS > > (Yes I think "alias" expresses the concept better) +1 IMHO I think /mentally/ ALIAS really "nails it". :) --Chris > > -- > Guido Falsi > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Fri Oct 6 20:31:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EC2EE41075 for ; Fri, 6 Oct 2017 20:31:50 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52C0D6EB3F for ; Fri, 6 Oct 2017 20:31:49 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-qk0-x22b.google.com with SMTP id b15so16957697qkg.9 for ; Fri, 06 Oct 2017 13:31:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+6Is7s3InkjJxdfMX8Lf0N9mfrpA24ZUQpTat9rK4O4=; b=0FvMlKublCJij2aOeJ9fhIsQv4xbio45wonnDZdQxnCtOEnLQIedlmdR0MBC+msKeh wfUDIpc6S6zIJJHuSfmFzil80mZnZBj9zRZLKLPeJopKe0kGc9jJMxk5xLKdHN0rqiw5 4Pc0A4vqsZj1L4x3ithUH/DfMzk6Jdf86MEhJQM0b+lsxuVs/eeDbn+OT2JMfLM3g7qz tZhkROcCLxy+IWDByKbJopB9NiDf7BjidEbgRfl2INrLS2BgUOJUtYz8x/KwkNo10IVc XSYoRnatUIQ2p3XwxbTHNYzE4aa1qovZajEKDcMn1tlKfe61uZYM2svcULeg7lMWi/pD yiiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+6Is7s3InkjJxdfMX8Lf0N9mfrpA24ZUQpTat9rK4O4=; b=Wm4lefQD731pa4Uep8QPnHemXvoJpanPs39VwV788+OOu/v9F/tc9C8LCDtpX+J1KD c2kFTMLtXvWZ4Iqd5/bQfAConhXmGNaGmvexKl/5q3SzNxD1gFEihyptfgKtxm9eiMXs nNAyxxQUZtOz2b4THRuW2WE2M9bSni2aXW3m7kXegfWYh+epyifm/fxTfBKWsO7j4bxb F/5Z+3rFjHbU9pyrfNyf+OF+8CA+visBMVrPI9dze3HFoo/52JCUITb0CuC9l3/6yojk xREBJ5ztxOQ9rBIFGvBH6BsvIej0lKOhWqYrJKqzGjXzq9XIqwNnnCf2p5ZlvOOat1d2 3I4A== X-Gm-Message-State: AMCzsaWVnWBsHwoKu0qNiwUIiid5eaZaxsIKYWojequ9LBqasfg3Xnyc 2JBCoXfXjEtY/4umHASebFfLfuzcN6mZ/PylanIiD0Bv X-Google-Smtp-Source: AOwi7QAfuDhAY3hkxEn6GwaebROWvfj+/tgnOv1/XBGadunoqlzVaG1mAaD9JKlE91jIq3X4kJb6GFEwHUQc4ZyM/4Y= X-Received: by 10.55.191.129 with SMTP id p123mr93528qkf.47.1507321908688; Fri, 06 Oct 2017 13:31:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.81.233 with HTTP; Fri, 6 Oct 2017 13:31:47 -0700 (PDT) X-Originating-IP: [150.107.174.148] In-Reply-To: References: From: Jonathan Chen Date: Sat, 7 Oct 2017 09:31:47 +1300 Message-ID: Subject: Re: Crashing chromium/iridium To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 20:31:50 -0000 On 7 October 2017 at 08:39, Grzegorz Junka wrote: > Just wanted to check if anybody else observed this annoying behaviour in > Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab > hangs loading for 30-60 seconds, after which time the browser shows a dialog > that the webpage doesn't load and I can either kill or wait. This bug has been around for a very long time: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 There was some anecdotal evidence that it was related to code-caching, with a possible workaround, but no fixes for it have been committed. The workarounds do not appear to work anymore with the latest updates, though. CHeers. -- Jonathan Chen From owner-freebsd-ports@freebsd.org Fri Oct 6 22:11:03 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D3E9E42C7B; Fri, 6 Oct 2017 22:11:03 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E86471D16; Fri, 6 Oct 2017 22:11:02 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8152A20EB1; Fri, 6 Oct 2017 18:11:00 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 06 Oct 2017 18:11:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=N2OCVv +hEih1cAFqTFZhfvqOdI+9Rc05apu0QKaof+s=; b=Uc4cIWrVDsDVvuSZYasery HMeGEaVC5ahyW4yuYHu64soLj7w9RweLo4pgxqRzoYbyzgMEX/6NnJi8XKE3HC3Y L1dthka/fZ4h49iVzd3nvP48AQRvaEi88AaD5eAoaVfaXgvtYksNH5A4ODRpbbrL RvRxY8xStzDrHrVyXNYlzZOgQPvRG9DJv9KMb5bZ1rSRZ8gHeB50g6Izx3jZsqNr SrN8/ZhY/egi5MpDiaqEi07kpX6CFMMoprRDZOmaQ/ynM1lxdW/6aeqBTuq7M6lw xgyCDDFx/ACpaPgDp+uJaEnguUtjmubWcOqu6y4Cyi2RFhx2zt5oU81iJU2zsGLQ == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=N2OCVv+hEih1cAFqTFZhfvqOdI+9Rc05apu0QKaof +s=; b=qD+nsJFZzPMykp92ELDyVDiVZhiYK1JYigOPBDZWXpozbHtssbKRpk6u5 Ns47mGolYPR6cW5GtYWPlZjBrNRE09C+zEVWfvnPS0r3rOb2aA97FU6/aihjDC9t kQfSY3zh87nyLWniaZGaaOBerJpM2kQFxscagU3v95P4Q79gaB0nmotHQvdMzqYS oDmd6bS7gbd1T9qL1ZRbz0WbhkdT98rRS9U7ikT2J6gCQss2aJ+yawPxv0UiaDIe l3kVL4RiacR/uzqMCv1jOHAXOeK6X0TrIGunbhGAwEurtfyTWGjrncGSy8WNT0so jtQOmf/q0rdB73Q4tsOTpvkYlSPhQ== X-ME-Sender: X-Sasl-enc: /lcpcA+CjzP/I2wwoqANqJiRlJbh30nOVsNbcQpqksMF 1507327860 Received: from v007.zyxst.net (v007.zyxst.net [89.145.100.139]) by mail.messagingengine.com (Postfix) with ESMTPA id EBD1C7F066; Fri, 6 Oct 2017 18:10:59 -0400 (EDT) Date: Fri, 6 Oct 2017 23:10:58 +0100 From: tech-lists To: freebsd-questions@freebsd.org Cc: freebsd-ports@freebsd.org Subject: make ports use system clang & llvm Message-ID: <20171006221058.GA98039@v007.zyxst.net> Mail-Followup-To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 22:11:03 -0000 Hello, Is there a way to make ports use system clang & llvm (now at v5) rather than pulling in llvm4? If so, please tell me what it is! thanks, -- J. From owner-freebsd-ports@freebsd.org Fri Oct 6 23:50:34 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6199E44479 for ; Fri, 6 Oct 2017 23:50:34 +0000 (UTC) (envelope-from gregthehun@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 865B774295 for ; Fri, 6 Oct 2017 23:50:34 +0000 (UTC) (envelope-from gregthehun@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 81FB4E44475; Fri, 6 Oct 2017 23:50:34 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 816BBE44474 for ; Fri, 6 Oct 2017 23:50:34 +0000 (UTC) (envelope-from gregthehun@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F13D74294; Fri, 6 Oct 2017 23:50:34 +0000 (UTC) (envelope-from gregthehun@gmail.com) Received: by mail-it0-x233.google.com with SMTP id 72so6623290itk.3; Fri, 06 Oct 2017 16:50:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=cagh9sqVYVkYhvILInEMJCCuIId/e18j9EAnJSmM/rU=; b=FvcCA7HIU1OEvNcTdDTikM2gUSowFA1wfqsFQ+O0km1QQRzkyksKJIRRilKglgy+fZ zB/7/Hw0YD7Dl9h36ZFRKdkvDBtTp58TclpNpy0rgRHhDO1CCJN/e54vuHQ9UkOb/J8K EIjh1Fe1cPl1J4yu4uhnSLjgzHb0rklphCMSvOePacBAMoXv57zOp9uRVjeW7+9QIWoG a+ZPYPQODsxf7jEvu1an4UGCzEM/2qRTXgu+XuvWYU7K1MydLKrxyCuNr9C9M+W23huc zxb25B4r/rx+MW8vEswdmLpc1uLVEvppeT3fsBg/+Q8yOOtvGFYHxE0+hinAmW1g7w4a 9ZnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=cagh9sqVYVkYhvILInEMJCCuIId/e18j9EAnJSmM/rU=; b=jfS9zQLEupBbS8aU5/zyIPikEhswv3VQfWM+ZC8QERkgOyWXii83orTHf8N7Q3yMdf 3CGl0yPm9kZyjjIiTvM2+j5jH6DaTxAub3opV+7zc99Kdm8WIqjfFcRo8n5YEOgP9JYq ypa1AIQnUDOI3AlFb+rC/9HN2P0FOasma7SPciW0DfbwD2dMhOFDE5F++0IqjfiJFprZ QkqLCKAvfgVPwLie0cdJfMKJVXTd5Dh4u4G2MhHF1ucZHsEol6JeHMhvaUH+1furYBkx GF8vjE4BBCeU30GFUdNSO1UIxTV6CgymNXmrQxnMv637KrJdTVQ6MLD64o4KoRLcpSVG 0hkA== X-Gm-Message-State: AMCzsaU986PX2WTRmv/6YGslo9f8NN3/GJBmy1ebOMrgDInP+9SynO8D 2keyJ1q0RajYcF67PsTN6krT8sPhPvmch4axI+c= X-Google-Smtp-Source: AOwi7QBi8rMVMqk67Y+td3OzsptRv1pTBrHwxhiK6WXtQ0tm5Upc5htuopuDJETARbP+qoME+8D6eszW/8nxQHztCBM= X-Received: by 10.36.19.71 with SMTP id 68mr4617378itz.150.1507333833527; Fri, 06 Oct 2017 16:50:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.44.83 with HTTP; Fri, 6 Oct 2017 16:49:53 -0700 (PDT) From: Greg Bedsaul Date: Fri, 6 Oct 2017 18:49:53 -0500 Message-ID: Subject: Kibana5 crashing after install leaving defaults To: tj@freebsd.org Cc: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 23:50:34 -0000 Well, the subject is pretty self explanitory, but I would love to give you any information about my system since it is more of a lab setup and I can delete it at will. Thank you -- Greg Bedsaul From owner-freebsd-ports@freebsd.org Sat Oct 7 02:58:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAC4EE2AE70; Sat, 7 Oct 2017 02:58:47 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9A7ED7E944; Sat, 7 Oct 2017 02:58:47 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 3B7965A9F12; Sat, 7 Oct 2017 02:58:40 +0000 (UTC) Date: Sat, 7 Oct 2017 02:58:40 +0000 From: Brooks Davis To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: make ports use system clang & llvm Message-ID: <20171007025839.GA68389@spindle.one-eyed-alien.net> References: <20171006221058.GA98039@v007.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <20171006221058.GA98039@v007.zyxst.net> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 02:58:47 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 06, 2017 at 11:10:58PM +0100, tech-lists wrote: > Hello, >=20 > Is there a way to make ports use system clang & llvm (now at v5) rather t= han=20 > pulling in llvm4? If so, please tell me what it is! Short verison: no. Longer version: Ports that depend on a specific LLVM version typically do so because they link to LLVM libraries. LLVM provides *no* API stability between releases so programs can only link to a narrow range of LLVM versions (1 version is common) and we can not ship the libraries with the base system because we would then be stuck with a single LLVM and clang version for the life of a STABLE branch (usually 5+ years). -- Brooks --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJZ2ELfAAoJEKzQXbSebgfAhBQH/2ZKrtO3p930178J/MSfOK0l 6U9gXdqZ8lw0+DaW0dVM/Yhy0N3SEvoRwGv67qorF9jpilkXgAVhAnW1cVIAfSIo YrYFgXsQg8AM+WzhdajFyKe4O/lLH/brQvczXX2/8mAA/g9NTpcGGtStfsYJo7bI If24qdzusA0h4OKrIhlqV9jbGSvMPRsluA2Nmx8K3YS9pfnbkH/csOIbS4VQaru2 OASYelV2ZI+iiscHu0F/OKadSyeOgQqXkt0vKk/OL0FRPmp4WmI7CiwkKAPzpIzk StwuhDgZJmoa5Wqvvc36AXJ/Kej4yH95Wy/kYu4Wg0BSsNpFwwZuNny0SWPob2M= =NYYn -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe-- From owner-freebsd-ports@freebsd.org Sat Oct 7 07:58:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36CE2E30F2F for ; Sat, 7 Oct 2017 07:58:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1CE7F3073 for ; Sat, 7 Oct 2017 07:58:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1C37EE30F2D; Sat, 7 Oct 2017 07:58:23 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BDF5E30F2C for ; Sat, 7 Oct 2017 07:58:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C2773071 for ; Sat, 7 Oct 2017 07:58:23 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v977wMsq082687 for ; Sat, 7 Oct 2017 07:58:22 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v977wMFM082686; Sat, 7 Oct 2017 07:58:22 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201710070758.v977wMFM082686@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sat, 7 Oct 2017 07:58:22 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 07:58:23 -0000 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/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/aws-sdk-cpp | 1.2.5 | 1.2.10 ------------------------------------------------+-----------------+------------ 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 Thanks. From owner-freebsd-ports@freebsd.org Sat Oct 7 11:21:46 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F0C5E35E2E for ; Sat, 7 Oct 2017 11:21:46 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19512849F4 for ; Sat, 7 Oct 2017 11:21:45 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 383A334638; Sat, 7 Oct 2017 13:12:54 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_B5C886FB-CE87-4EA8-A0DB-B3E7938F9A46"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: collectd5 pkg upgrade pulls in 72 new dependencies? Date: Sat, 7 Oct 2017 13:12:53 +0200 In-Reply-To: <2ce0d4f8-5f45-e237-e6f7-32b8e9fac736@nomadlogic.org> Cc: freebsd-ports@freebsd.org To: Pete Wright References: <2ce0d4f8-5f45-e237-e6f7-32b8e9fac736@nomadlogic.org> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 11:21:46 -0000 --Apple-Mail=_B5C886FB-CE87-4EA8-A0DB-B3E7938F9A46 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 5 Oct 2017, at 18:06, Pete Wright wrote: >=20 > hey there - i was doing usual maintaince on my systems today and = noticed that when upgrading the collectd5 pkg it pulls in 72 new = dependencies, mostly xorg related. here's a gist of the upgrade command = exhibiting this. the platform 11.1-RELEASE: >=20 > https://gist.github.com/nomadlogic/53e81ba377a4a475351c3b8309be7598 >=20 > is this expected? maybe i missed a heads up email to this list? =46rom which version did you upgrade? The most recent change to the = port is that the DEBUG, GCRYPT and PING options were enabled by default, here: https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D449798 However, the only dependencies added because of it are libgcrypt and liboping, which should not really be dependent on any xorg stuff. -Dimitry --Apple-Mail=_B5C886FB-CE87-4EA8-A0DB-B3E7938F9A46 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWdi2tQAKCRCwXqMKLiCW o71WAKDRtE2RdM10GVAjHhHSdcKrZpjI0wCfdUnr3xoyAZDzk0OQQeosS49VfQc= =OijO -----END PGP SIGNATURE----- --Apple-Mail=_B5C886FB-CE87-4EA8-A0DB-B3E7938F9A46-- From owner-freebsd-ports@freebsd.org Sat Oct 7 14:54:26 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 542BAE3A387 for ; Sat, 7 Oct 2017 14:54:26 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DCD56A6B6; Sat, 7 Oct 2017 14:54:25 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1507388057; bh=1Qj/OcWkgxtl6W0RS6sZFVgBlirNAAn5EmlYCsF HtrQ=; b=qC4ZtWBhR1lejRvPqCtGqsb3YQ4v5+DmCxdK8eX0KxK9A1AhbmuCOTl hgaogP6DOCFhKhGTiFKeUP2513pd1RztJXpNCAOJZxUI99Sg/rM7Wt049TE5DueQ YmtUHR5TbiY1ZlPyaTX8syoL85Mznneq16V1XBUJ8IXz4h2HGzdM= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 9C637258EA; Sat, 7 Oct 2017 10:54:17 -0400 (EDT) To: FreeBSD Ports , tobik@freebsd.org From: Michael Butler Subject: netpbm broken at SVN r451378 on -current Message-ID: Date: Sat, 7 Oct 2017 10:54:16 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 14:54:26 -0000 Building fails with .. cc -o ppmtompeg ppmtompeg.o mfwddct.o postdct.o huff.o bitio.o mheaders.o mpeg.o subsample.o param.o rgbtoycc.o readframe.o combine.o jrevdct.o frame.o fsize.o frametype.o specifics.o rate.o opts.o input.o parallel.o psocket.o gethostname.o frames.o iframe.o pframe.o bframe.o psearch.o bsearch.o block.o jpeg.o -L/usr/local/lib -ljpeg -L/usr/ports/graphics/netpbm/work/netpbm-10.80.00/lib -lnetpbm -fstack-protector -lm ppmtompeg.o: In function `main': ppmtompeg.c:(.text+0x99c): undefined reference to `pm_strfree' ppmtompeg.o: In function `getUserFrameFile': ppmtompeg.c:(.text+0xca1): undefined reference to `pm_asprintf' ppmtompeg.c:(.text+0xceb): undefined reference to `pm_strfree' ppmtompeg.c:(.text+0xcf4): undefined reference to `pm_strfree' ppmtompeg.o: In function `encodeSomeFrames': ppmtompeg.c:(.text+0xd5e): undefined reference to `pm_asprintf' ppmtompeg.c:(.text+0xd71): undefined reference to `pm_asprintf' ppmtompeg.c:(.text+0xdb2): undefined reference to `pm_strfree' ppmtompeg.c:(.text+0xdbb): undefined reference to `pm_strfree' mpeg.o: In function `GenMPEGStream': mpeg.c:(.text+0x92d): undefined reference to `pm_asprintf' mpeg.c:(.text+0x953): undefined reference to `pm_strfree' mpeg.c:(.text+0xa09): undefined reference to `pm_asprintf' mpeg.c:(.text+0xa24): undefined reference to `pm_strfree' mpeg.c:(.text+0xedd): undefined reference to `pm_asprintf' mpeg.c:(.text+0xef8): undefined reference to `pm_strfree' .. what am I missing here? imb From owner-freebsd-ports@freebsd.org Sat Oct 7 14:58:54 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5AB4E3A46E for ; Sat, 7 Oct 2017 14:58:54 +0000 (UTC) (envelope-from tobik@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A29ED6B511 for ; Sat, 7 Oct 2017 14:58:54 +0000 (UTC) (envelope-from tobik@FreeBSD.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7E94220B4D; Sat, 7 Oct 2017 10:58:53 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Sat, 07 Oct 2017 10:58:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=EFma80 QPQir9vqi6J1y203afRGziV0elpqCWm766v2g=; b=c2cDCMq/utFIBR5Q3xIPwu +6skMEmJCx5UXm33qrxF6V7utFCGgsA/1gy+hcjYR/jTCHtWoudAcX4O64KV84UE i7RxbQdO8aXtvzYlPKi0irjaalThGr3oK3X4k+TsN8Y85OJqpopqiLXc91LYt1b1 VTpRCuq4JdHHoGHM1Nj9ypy93U+aH309fOtRLGS6MMgfPwdLxh6LTFy8aff6VLG1 SilR2y2rvgHk5mOjUcVl93RAZEiZjIus0w1xosf0Lt5fM29+ZkhrnjFI5U5Wnf6M hH1CcRD/RtLvuBYQHxd1w49EdiluTh9Diugv4xygmW4Z6/WxQ7JFbKqI5lS+GtQQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 5F2F19E305; Sat, 7 Oct 2017 10:58:53 -0400 (EDT) Message-Id: <1507388333.4087069.1131048736.05924D26@webmail.messagingengine.com> From: Tobias Kortkamp To: Michael Butler , FreeBSD Ports MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-26fdae60 Subject: Re: netpbm broken at SVN r451378 on -current In-Reply-To: Date: Sat, 07 Oct 2017 16:58:53 +0200 References: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 14:58:55 -0000 On Sat, Oct 7, 2017, at 16:54, Michael Butler wrote: > Building fails with .. > > cc -o ppmtompeg ppmtompeg.o mfwddct.o postdct.o huff.o bitio.o > mheaders.o mpeg.o subsample.o param.o rgbtoycc.o readframe.o combine.o > jrevdct.o frame.o fsize.o frametype.o specifics.o rate.o opts.o input.o > parallel.o psocket.o gethostname.o frames.o iframe.o pframe.o bframe.o > psearch.o bsearch.o block.o jpeg.o -L/usr/local/lib -ljpeg > -L/usr/ports/graphics/netpbm/work/netpbm-10.80.00/lib -lnetpbm > -fstack-protector -lm > ppmtompeg.o: In function `main': > ppmtompeg.c:(.text+0x99c): undefined reference to `pm_strfree' > ppmtompeg.o: In function `getUserFrameFile': > ppmtompeg.c:(.text+0xca1): undefined reference to `pm_asprintf' > ppmtompeg.c:(.text+0xceb): undefined reference to `pm_strfree' > ppmtompeg.c:(.text+0xcf4): undefined reference to `pm_strfree' > ppmtompeg.o: In function `encodeSomeFrames': > ppmtompeg.c:(.text+0xd5e): undefined reference to `pm_asprintf' > ppmtompeg.c:(.text+0xd71): undefined reference to `pm_asprintf' > ppmtompeg.c:(.text+0xdb2): undefined reference to `pm_strfree' > ppmtompeg.c:(.text+0xdbb): undefined reference to `pm_strfree' > mpeg.o: In function `GenMPEGStream': > mpeg.c:(.text+0x92d): undefined reference to `pm_asprintf' > mpeg.c:(.text+0x953): undefined reference to `pm_strfree' > mpeg.c:(.text+0xa09): undefined reference to `pm_asprintf' > mpeg.c:(.text+0xa24): undefined reference to `pm_strfree' > mpeg.c:(.text+0xedd): undefined reference to `pm_asprintf' > mpeg.c:(.text+0xef8): undefined reference to `pm_strfree' > > .. what am I missing here? See /usr/ports/UPDATING. Uninstall the old netpbm first. From owner-freebsd-ports@freebsd.org Sat Oct 7 16:31:31 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D08FCE3BE76 for ; Sat, 7 Oct 2017 16:31:31 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DFB18292C; Sat, 7 Oct 2017 16:31:31 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e0s0S-000L6c-7V; Sat, 07 Oct 2017 10:31:16 -0600 Date: Sat, 7 Oct 2017 10:31:16 -0600 From: The Doctor To: Tobias Kortkamp Cc: Michael Butler , FreeBSD Ports Subject: Re: netpbm broken at SVN r451378 on -current Message-ID: <20171007163116.GA79597@doctor.nl2k.ab.ca> References: <1507388333.4087069.1131048736.05924D26@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1507388333.4087069.1131048736.05924D26@webmail.messagingengine.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 16:31:32 -0000 On Sat, Oct 07, 2017 at 04:58:53PM +0200, Tobias Kortkamp wrote: > On Sat, Oct 7, 2017, at 16:54, Michael Butler wrote: > > Building fails with .. > > > > cc -o ppmtompeg ppmtompeg.o mfwddct.o postdct.o huff.o bitio.o > > mheaders.o mpeg.o subsample.o param.o rgbtoycc.o readframe.o combine.o > > jrevdct.o frame.o fsize.o frametype.o specifics.o rate.o opts.o input.o > > parallel.o psocket.o gethostname.o frames.o iframe.o pframe.o bframe.o > > psearch.o bsearch.o block.o jpeg.o -L/usr/local/lib -ljpeg > > -L/usr/ports/graphics/netpbm/work/netpbm-10.80.00/lib -lnetpbm > > -fstack-protector -lm > > ppmtompeg.o: In function `main': > > ppmtompeg.c:(.text+0x99c): undefined reference to `pm_strfree' > > ppmtompeg.o: In function `getUserFrameFile': > > ppmtompeg.c:(.text+0xca1): undefined reference to `pm_asprintf' > > ppmtompeg.c:(.text+0xceb): undefined reference to `pm_strfree' > > ppmtompeg.c:(.text+0xcf4): undefined reference to `pm_strfree' > > ppmtompeg.o: In function `encodeSomeFrames': > > ppmtompeg.c:(.text+0xd5e): undefined reference to `pm_asprintf' > > ppmtompeg.c:(.text+0xd71): undefined reference to `pm_asprintf' > > ppmtompeg.c:(.text+0xdb2): undefined reference to `pm_strfree' > > ppmtompeg.c:(.text+0xdbb): undefined reference to `pm_strfree' > > mpeg.o: In function `GenMPEGStream': > > mpeg.c:(.text+0x92d): undefined reference to `pm_asprintf' > > mpeg.c:(.text+0x953): undefined reference to `pm_strfree' > > mpeg.c:(.text+0xa09): undefined reference to `pm_asprintf' > > mpeg.c:(.text+0xa24): undefined reference to `pm_strfree' > > mpeg.c:(.text+0xedd): undefined reference to `pm_asprintf' > > mpeg.c:(.text+0xef8): undefined reference to `pm_strfree' > > > > .. what am I missing here? > > See /usr/ports/UPDATING. Uninstall the old netpbm first. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" IS their a way around uninstalling? I would have to reinstall 45 ports. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and he calls you foolish - Euripides From owner-freebsd-ports@freebsd.org Sat Oct 7 16:39:07 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4792CE3BF6F for ; Sat, 7 Oct 2017 16:39:07 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE594841F1; Sat, 7 Oct 2017 16:39:06 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1507394345; bh=czyI7Gkw ihHy9Skhob2432FfQNOTSQFc2uwB9vGnTIE=; b=UH3pDOx4JjW6PDigxSbNmTix VABdG9EP5nJJ5R3XaO5OUPJ05OHQMi/M7GC5yjH2nZcTbOXtS9qykTK+rlZ8z+kl LJaEJ16OebNmWpl+nSzQ/oOGqPKmRoAB+K7QviKYSSFp6ZiX9NtzdNYB9s81enzZ k+097b4Ilhd7S2zcki8= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 128FE27CB8; Sat, 7 Oct 2017 12:39:05 -0400 (EDT) Subject: Re: netpbm broken at SVN r451378 on -current To: The Doctor , Tobias Kortkamp Cc: FreeBSD Ports References: <1507388333.4087069.1131048736.05924D26@webmail.messagingengine.com> <20171007163116.GA79597@doctor.nl2k.ab.ca> From: Michael Butler Message-ID: Date: Sat, 7 Oct 2017 12:39:04 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171007163116.GA79597@doctor.nl2k.ab.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 16:39:07 -0000 On 10/07/17 12:31, The Doctor wrote: > > IS their a way around uninstalling? > > I would have to reinstall 45 ports. use "pkg delete -f netpbm" before reinstalling, imb From owner-freebsd-ports@freebsd.org Sat Oct 7 16:42:51 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A1C7E3C2FC for ; Sat, 7 Oct 2017 16:42:51 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [50.197.129.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pozo.com", Issuer "pozo.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E50FF147; Sat, 7 Oct 2017 16:42:50 +0000 (UTC) (envelope-from null@pozo.com) Received: from 50-197-129-138-static.hfc.comcastbusiness.net (octo.pozo.com [192.168.0.2]) (authenticated bits=128) by pozo.com (8.15.2/8.15.2) with ESMTPA id v97GfHjn077233; Sat, 7 Oct 2017 09:41:17 -0700 (PDT) (envelope-from null@pozo.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: netpbm broken at SVN r451378 on -current From: Manfred Antar In-Reply-To: <20171007163116.GA79597@doctor.nl2k.ab.ca> Date: Sat, 7 Oct 2017 09:41:17 -0700 Cc: Tobias Kortkamp , Michael Butler , FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: <6B701FE9-EE06-4705-ABF2-744437970C56@pozo.com> References: <1507388333.4087069.1131048736.05924D26@webmail.messagingengine.com> <20171007163116.GA79597@doctor.nl2k.ab.ca> To: The Doctor X-Mailer: Apple Mail (2.3445.1.7) X-Spam-Status: No, score=-102.2 required=5.0 tests=ALL_TRUSTED,BAYES_00, J_CHICKENPOX_75,TW_TP,URIBL_BLOCKED,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1, No X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: v97GfHjn077233 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 16:42:51 -0000 pkg delete -f netpbm will work, it will only install netpbm. then you can build and install netpbm. use libchk to find which ports are broken with new netpbm and rebuild them > On Oct 7, 2017, at 9:31 AM, The Doctor wrote: >=20 > On Sat, Oct 07, 2017 at 04:58:53PM +0200, Tobias Kortkamp wrote: >> On Sat, Oct 7, 2017, at 16:54, Michael Butler wrote: >>> Building fails with .. >>>=20 >>> cc -o ppmtompeg ppmtompeg.o mfwddct.o postdct.o huff.o bitio.o=20 >>> mheaders.o mpeg.o subsample.o param.o rgbtoycc.o readframe.o combine.o= =20 >>> jrevdct.o frame.o fsize.o frametype.o specifics.o rate.o opts.o input.o= =20 >>> parallel.o psocket.o gethostname.o frames.o iframe.o pframe.o bframe.o= =20 >>> psearch.o bsearch.o block.o jpeg.o -L/usr/local/lib -ljpeg=20 >>> -L/usr/ports/graphics/netpbm/work/netpbm-10.80.00/lib -lnetpbm=20 >>> -fstack-protector -lm >>> ppmtompeg.o: In function `main': >>> ppmtompeg.c:(.text+0x99c): undefined reference to `pm_strfree' >>> ppmtompeg.o: In function `getUserFrameFile': >>> ppmtompeg.c:(.text+0xca1): undefined reference to `pm_asprintf' >>> ppmtompeg.c:(.text+0xceb): undefined reference to `pm_strfree' >>> ppmtompeg.c:(.text+0xcf4): undefined reference to `pm_strfree' >>> ppmtompeg.o: In function `encodeSomeFrames': >>> ppmtompeg.c:(.text+0xd5e): undefined reference to `pm_asprintf' >>> ppmtompeg.c:(.text+0xd71): undefined reference to `pm_asprintf' >>> ppmtompeg.c:(.text+0xdb2): undefined reference to `pm_strfree' >>> ppmtompeg.c:(.text+0xdbb): undefined reference to `pm_strfree' >>> mpeg.o: In function `GenMPEGStream': >>> mpeg.c:(.text+0x92d): undefined reference to `pm_asprintf' >>> mpeg.c:(.text+0x953): undefined reference to `pm_strfree' >>> mpeg.c:(.text+0xa09): undefined reference to `pm_asprintf' >>> mpeg.c:(.text+0xa24): undefined reference to `pm_strfree' >>> mpeg.c:(.text+0xedd): undefined reference to `pm_asprintf' >>> mpeg.c:(.text+0xef8): undefined reference to `pm_strfree' >>>=20 >>> .. what am I missing here? >>=20 >> See /usr/ports/UPDATING. Uninstall the old netpbm first. >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >=20 > IS their a way around uninstalling? >=20 > I would have to reinstall 45 ports. >=20 > --=20 > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2= k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist = rising! > https://www.empire.kred/ROOTNK?t=3D94a1f39b Look at Psalms 14 and 53 on = Atheism > Talk Sense to a fool and he calls you foolish - Euripides > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >=20 > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-ports@freebsd.org Sat Oct 7 17:48:12 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EA60E3DC92 for ; Sat, 7 Oct 2017 17:48:12 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from lb1-smtp-cloud8.xs4all.net (lb1-smtp-cloud8.xs4all.net [194.109.24.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.xs4all.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA3BB6DBD2 for ; Sat, 7 Oct 2017 17:48:11 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan ([83.160.85.125]) by smtp-cloud8.xs4all.net with ESMTP id 0tCjeLAsDg5cR0tCkeDpZW; Sat, 07 Oct 2017 19:48:03 +0200 Received: from yokozuna (yokozuna [IPv6:0:0:0:0:0:0:0:1]) by yokozuna.lan (8.15.2/8.15.2) with ESMTPS id v97Hm0hE004017 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 7 Oct 2017 19:48:01 +0200 (CEST) (envelope-from mbeis@xs4all.nl) Date: Sat, 7 Oct 2017 19:48:00 +0200 (CEST) From: Marco Beishuizen Sender: marco@yokozuna.lan Reply-To: Marco Beishuizen To: freebsd-ports@freebsd.org Subject: Request to commit update x11-wm/windowmaker to 0.95.8 Message-ID: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-CMAE-Envelope: MS4wfD/G2dhoURTMEhkkyjBrf3RBQ7giyzK1RBtBFzBngZ1oC9pOVbIgpCg/iHaAgpulJgRpdOsE+drT7Vin9vJri9AiFFz2FF6jdYNdq0EhOfswbWc9VROY VnepiGJEdQakb6gWsT5XTOTcPiq2TkuoXLFM8RszLxwswk99AulAz2K/ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 17:48:12 -0000 Hi, I submitted a patch to update x11-wm/windowmaker to 0.95.8 over 3 months ago but there is no response from the maintainer. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220058 Is it possible to get this patch reviewed/committed? Thanks in advance, Regards, Marco -- A newspaper is a circulating library with high blood pressure. -- Arthure "Bugs" Baer From owner-freebsd-ports@freebsd.org Sat Oct 7 21:12:47 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83234E427C7 for ; Sat, 7 Oct 2017 21:12:47 +0000 (UTC) (envelope-from pz-freebsd-ports@ziemba.us) Received: from osmtp.ziemba.us (osmtp.ziemba.us [208.106.105.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD35B7E13A for ; Sat, 7 Oct 2017 21:12:46 +0000 (UTC) (envelope-from pz-freebsd-ports@ziemba.us) Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1]) by hairball.ziemba.us (8.15.2/8.15.2) with ESMTP id v97Kiec4011254 for ; Sat, 7 Oct 2017 13:44:40 -0700 (PDT) (envelope-from pz-freebsd-ports@ziemba.us) Received: (from mailnull@localhost) by hairball.ziemba.us (8.15.2/8.15.2/Submit) id v97Kieb2011253 for freebsd-ports@freebsd.org; Sat, 7 Oct 2017 13:44:40 -0700 (PDT) (envelope-from pz-freebsd-ports@ziemba.us) X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to pz-freebsd-ports@ziemba.us using -f Received: (from news@localhost) by usenet.ziemba.us (8.14.5/8.14.5/Submit) id v97KiLnX055434 for treehouse-mail-freebsd-ports@hairball.ziemba.us; Sat, 7 Oct 2017 13:44:21 -0700 (PDT) (envelope-from news) From: "G. Paul Ziemba" To: freebsd-ports@freebsd.org Subject: Re: Crashing chromium/iridium Date: Sat, 7 Oct 2017 20:44:21 +0000 (UTC) Message-id: References: Reply-to: unp@ziemba.us Errors-to: "G. Paul Ziemba" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 21:12:47 -0000 jonc@chen.org.nz (Jonathan Chen) writes: >On 7 October 2017 at 08:39, Grzegorz Junka wrote: >> Just wanted to check if anybody else observed this annoying behaviour in >> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab >> hangs loading for 30-60 seconds, after which time the browser shows a dialog >> that the webpage doesn't load and I can either kill or wait. >This bug has been around for a very long time: >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 >There was some anecdotal evidence that it was related to code-caching, >with a possible workaround, but no fixes for it have been committed. >The workarounds do not appear to work anymore with the latest updates, >though. The following applies to FreeBSD 11-stable. I did not experience the issue with 51.0.2704.84, but have seen it since chrome 59.0.3071.115. I also tried 60.0.3112.101 and 61.0.3163.100 (more recent versions of the www/chromium port) with no improvement. Might be an independent bug, but I am also getting a "file not found" error when I click on "options" for the three different plugins I was using ("ublock origin", "tabs outliner", and "go back with backspace"). This broken behavior could be fixed temporarily by deleting and then reinstalling the plugin, but after a day or so it would return. I found that I could recover from the "some tabs hanging forever" state by: 1. Quit chrome browser 2. Delete cache in ~/.cache/chromium or wherever (I am using --user-data-dir=/my/homedir/.config/chrome-myhostname, and it appears to affect the path in ~/.cache as well) 3. Delete user data dir (in my case, /my/homedir/.config/chrome-myhostname) 4. Restore Bookmarks file (I copy it via cron every day) 5. Reinstall "ublock origin". I abandoned the other two plugins because T.O. couldn't access its configuration and the backspace plugin stopped working (grr) That is a drastic approach because all configuration and state is lost, but it did seem to overcome the hanging tab problem. It makes me think that there is some persistent state in chrome's user directory that is related to this issue. I tried building www/chromium 61 with DEBUG, but the build failed, and I have not pursued it further. -- G. Paul Ziemba FreeBSD unix: 1:41PM up 9 days, 23:29, 14 users, load averages: 0.38, 0.35, 0.29