Re: Removing documentation

2016-02-09 Thread Torsten Zühlsdorff
On 08.02.2016 01:02, Warren Block wrote: On Sun, 7 Feb 2016, Torsten Zühlsdorff wrote: Hello, You have a tool presented as "official" that hasn't had it's original maintainer in 4 years and was only kept on life support up until 9 months ago. Agreed, the "official" (the term used is

Re: Removing documentation

2016-02-09 Thread Torsten Zühlsdorff
On 08.02.2016 02:18, Greg 'groggy' Lehey wrote: On Sunday, 7 February 2016 at 12:44:32 +0100, Torsten Zühlsdorff wrote: Hello, You have a tool presented as "official" that hasn't had it's original maintainer in 4 years and was only kept on life support up until 9 months ago. Agreed, the

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 7:20 PM, Warren Block wrote: >> If you have the build log, I'd like to see it. Dewayne G. got an error >> after overriding CPUTYPE (do you do that too?) and I'm thinking it's >> sensitive to CPU and I'd like to know more. > > Yes, I use > > CPUTYPE?=core-avx2 What happens when you

maintaining portmaster ? was: Re: Removing documentation

2016-02-09 Thread Kurt Jaeger
Hi! Torsten wrote: > I did take a look. I could do both: maintaining the port and maintaining > the software. What do you need? ;) Submit patches to the 12 PRs open for portmaster: https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster -- p...@opsec.eu+49 171

Re: Removing documentation

2016-02-09 Thread Ernie Luzar
Kevin Oberman wrote: On Sat, Feb 6, 2016 at 4:03 PM, Greg 'groggy' Lehey wrote: I'm bringing this to the attention of the ports community to try to come up with a consensus about how to handle existing documentation for ageing packages, in this case portmaster. This bug

Re: Removing documentation (was: [Bug 206922] Handbook: Chapter 4.5+ changes)

2016-02-09 Thread Baptiste Daroussin
On Sun, Feb 07, 2016 at 11:03:04AM +1100, Greg 'groggy' Lehey wrote: > I'm bringing this to the attention of the ports community to try to > come up with a consensus about how to handle existing documentation > for ageing packages, in this case portmaster. > > This bug report suggests removing

FreeBSD ports you maintain which are out of date

2016-02-09 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 11:52 AM, Hrant Dadivanyan wrote: > It's fine that there is such an excellent tool as synth, but in server > environment, when only a few ports are installed, having a management port > with 17 dependencies is not reasonable. Rather that parroting this phrase, I would like to see

Re: Removing documentation

2016-02-09 Thread Hrant Dadivanyan
> > Then allow me to be the second. But then, I find poudriere > > unusable on my build system (I don't use ZFS and my memory is > > apparently too limited). Portmaster just does the right thing. > > > > We get that you don't like portmaster. So please don't use it. > > But don't deprive the

Re: Removing documentation

2016-02-09 Thread Baptiste Daroussin
On Tue, Feb 09, 2016 at 04:02:53PM +0800, Ernie Luzar wrote: > Kevin Oberman wrote: > > On Sat, Feb 6, 2016 at 4:03 PM, Greg 'groggy' Lehey > > wrote: > > > >> I'm bringing this to the attention of the ports community to try to > >> come up with a consensus about how to handle

Re: PHP7 package?

2016-02-09 Thread loic . blot
I have miwi ports running in production since 3 weeks without any issue, could be good to do last reviews and merge ? 7 février 2016 18:46 "Mathias Picker" a écrit: > Am 7. Februar 2016 17:19:05 MEZ, schrieb Dan Busarow > : > >> On

Re: Removing documentation

2016-02-09 Thread Jim Ohlstein
On 2/9/16 9:08 AM, John Marino wrote: On 2/9/2016 2:46 PM, Jim Ohlstein wrote: After all of this "discussion" I decided to give synth a try. I have no pony in this race as I use neither portmaster nor portupgrade. Both may still be in my repo, but they are not installed. Thanks for trying

Re: tor logging

2016-02-09 Thread William A. Mahaffey III
On 02/08/16 23:51, Kevin Oberman wrote: On Mon, Feb 8, 2016 at 9:16 PM, William A. Mahaffey III > wrote: On 02/08/16 15:52, Polytropon wrote: On Mon, 8 Feb 2016 15:36:58 -0553.75, William A. Mahaffey III wrote: My torrc

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 2:46 PM, Jim Ohlstein wrote: > After all of this "discussion" I decided to give synth a try. I have no > pony in this race as I use neither portmaster nor portupgrade. Both may > still be in my repo, but they are not installed. Thanks for trying it! > > The build time of "like 20-30

Re: port maintainer address

2016-02-09 Thread Michelle Sullivan
qjail1 wrote: > Kurt Jaeger wrote: >> Hi! >> >>> A year ago I was receiving loads of spam email on the maintainer >>> email addresses used in the ports makefile. I created bug tickets to >>> change the user name part of the email address for all the ports I >>> maintain, but some how I missed the

Re: Removing documentation

2016-02-09 Thread Hrant Dadivanyan
> On 2/9/2016 11:52 AM, Hrant Dadivanyan wrote: > > It's fine that there is such an excellent tool as synth, but in server > > environment, when only a few ports are installed, having a management port > > with 17 dependencies is not reasonable. > > Rather that parroting this phrase, I would

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 12:45 PM, Hrant Dadivanyan wrote: >> 1) As was just stated earler this morning, having synth installed is 2 >> packages: Synth itself and ncurses. These "17 dependences" are build >> requirements and not installed. So what is "unreasonable" about that? > > So will require any

avahi stops working?

2016-02-09 Thread Mark Felder
Is anyone else using avahi and experiencing weird reliability issues? On the one machine I run avahi on which is tracking CURRENT it seems to stop advertising to the network after a few minutes. Restarting it fixes it and then all my apple devices see the file server again. It's really annoying.

Re: Removing documentation

2016-02-09 Thread Jim Ohlstein
Hello, On 2/9/16 7:05 AM, John Marino wrote: On 2/9/2016 12:45 PM, Hrant Dadivanyan wrote: 1) As was just stated earler this morning, having synth installed is 2 packages: Synth itself and ncurses. These "17 dependences" are build requirements and not installed. So what is "unreasonable"

Re: Removing documentation

2016-02-09 Thread Royce Williams
IMO, this entire thread is masking a deeper symptom: FreeBSD ports/packages management is fragmented. Each unofficial tool treats some symptoms well, and others poorly. The fact that I have to use the phrase "ports/packages" is indicative of a deep schizophrenia. Don't get me wrong -- I love the

Re: Removing documentation

2016-02-09 Thread Warren Block
On Tue, 9 Feb 2016, Jim Ohlstein wrote: The build time of "like 20-30 minutes, at most" is ummm... let' just call it optimistic. I only needed five new dependencies. Poudriere was unable to take advantage of more than two parallel builders except for a rather short overlap where it used

Re: Removing documentation

2016-02-09 Thread William A. Mahaffey III
On 02/09/16 09:56, Royce Williams wrote: IMO, this entire thread is masking a deeper symptom: FreeBSD ports/packages management is fragmented. Each unofficial tool treats some symptoms well, and others poorly. The fact that I have to use the phrase "ports/packages" is indicative of a deep

Re: Removing documentation

2016-02-09 Thread Royce Williams
On Tue, Feb 9, 2016 at 6:50 AM, Royce Williams wrote: > IMO, this entire thread is masking a deeper symptom: FreeBSD > ports/packages management is fragmented. [snip] > We need to capture users' reasons for preferring specific frameworks, > and build a roadmap to how they could

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 5:00 PM, Warren Block wrote: > 2:20, that's two hours and twenty minutes, to build and install here on > an Atom N270 system. 2:06 for gcc6-aux, most of the rest for ncurses. > That does not include distfile download time. Disk space used was 252M, > again not counting the distfiles.

Re: Removing documentation

2016-02-09 Thread Warren Block
On Tue, 9 Feb 2016, John Marino wrote: On 2/9/2016 7:20 PM, Warren Block wrote: If you have the build log, I'd like to see it. Dewayne G. got an error after overriding CPUTYPE (do you do that too?) and I'm thinking it's sensitive to CPU and I'd like to know more. Yes, I use

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 9:20 PM, Warren Block wrote: > On Tue, 9 Feb 2016, John Marino wrote: > >> On 2/9/2016 7:20 PM, Warren Block wrote: If you have the build log, I'd like to see it. Dewayne G. got an error after overriding CPUTYPE (do you do that too?) and I'm thinking it's sensitive to

Re: Removing documentation

2016-02-09 Thread Warren Block
On Tue, 9 Feb 2016, John Marino wrote: On 2/9/2016 5:00 PM, Warren Block wrote: 2:20, that's two hours and twenty minutes, to build and install here on an Atom N270 system. 2:06 for gcc6-aux, most of the rest for ncurses. That does not include distfile download time. Disk space used was

Re: Removing documentation

2016-02-09 Thread Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/ 9/16 01:20 PM, Warren Block wrote: > On Tue, 9 Feb 2016, John Marino wrote: > >> On 2/9/2016 5:00 PM, Warren Block wrote: >>> 2:20, that's two hours and twenty minutes, to build and install >>> here on an Atom N270 system. 2:06 for

Re: PHP7 package?

2016-02-09 Thread Dan Busarow
On 2/7/16 9:54 AM, Kurt Jaeger wrote: > Hi! > >>> If you clone the repo from miwi, use it to build your own pkg repo, >>> you can use pkg upgrade to install those packages. > >>> That's how I did it my testbox. If you need more details on how to do it, >>> I can add a few more details. >> >>

Re: PHP7 package?

2016-02-09 Thread Waitman Gobble
On 2016-02-09 17:08, Dan Busarow wrote: On 2/7/16 9:54 AM, Kurt Jaeger wrote: Hi! If you clone the repo from miwi, use it to build your own pkg repo, you can use pkg upgrade to install those packages. That's how I did it my testbox. If you need more details on how to do it, I can add a

synth documentation (was: Removing documentation)

2016-02-09 Thread Greg 'groggy' Lehey
On Tuesday, 9 February 2016 at 15:08:22 +0100, John Marino wrote: > > Do you think the illustrated README on the github page is helpful? > > https://github.com/jrmarino/synth I looked at that a couple of days ago. It's certainly much better than anything else I've seen on github, but it's still

Re: synth documentation (was: Removing documentation)

2016-02-09 Thread Dave Horsfall
On Wed, 10 Feb 2016, Greg 'groggy' Lehey wrote: > I installed the synth package a couple of days ago, mainly to take a > look. And yes, I agree, if you're happy with the package (I would be), > the Ada dependencies and long build times aren't an issue. I'm sure the > learning curve isn't

Re: PHP7 package?

2016-02-09 Thread Kurt Jaeger
Hi! > Everythig seemed to work fine but when I added > > LoadModule php7_modulelibexec/apache24/libphp7.so > > to the httpd.conf apache core dumped. Ah, that is a different issue. Use https://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh on

Re: maintaining portmaster ? was: Re: Removing documentation

2016-02-09 Thread Peter Jeremy
On 2016-Feb-09 21:24:56 +0100, Kurt Jaeger wrote: >Torsten wrote: > >> I did take a look. I could do both: maintaining the port and maintaining >> the software. What do you need? ;) > >Submit patches to the 12 PRs open for portmaster: >

Re: Removing documentation

2016-02-09 Thread John Marino
On 2/9/2016 4:15 PM, Lars Engels wrote: > > root@fbsd01:~ # synth status > Querying system about current package installations. > Stand by, comparing installed packages against the ports tree. > Stand by, building pkg(8) first ... Failed!! (Synth must exit) > Unfortunately, the system upgrade