Kibana5 crashing after install leaving defaults

2017-10-06 Thread Greg Bedsaul 
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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

make ports use system clang & llvm

2017-10-06 Thread tech-lists 

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.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Crashing chromium/iridium

2017-10-06 Thread Jonathan Chen 
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 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [RFC] less patches: control the PATH

2017-10-06 Thread Chris H 
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-unsubscr...@freebsd.org"


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

Re: Crashing chromium/iridium

2017-10-06 Thread Kyle Evans 
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=729534 -- 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’ve found this to be an issue as well. None of the things that I’ve seen
> suggested online could fix it, and unfortunately do not have time to look
> at it myself. I’d be interested to hear if anyone has any more details
> regarding this issue.
>
> —
> Domagoj
>
> > On 6 Oct 2017, at 20: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.
> >
> > 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
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Crashing chromium/iridium

2017-10-06 Thread Domagoj Stolfa 
I’ve found this to be an issue as well. None of the things that I’ve seen 
suggested online could fix it, and unfortunately do not have time to look at it 
myself. I’d be interested to hear if anyone has any more details regarding this 
issue.

—
Domagoj

> On 6 Oct 2017, at 20: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.
> 
> 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
> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



signature.asc
Description: Message signed with OpenPGP

Crashing chromium/iridium

2017-10-06 Thread Grzegorz Junka 
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


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

Re: portmaster, portupgrade, etc

2017-10-06 Thread Chris H 
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-unsubscr...@freebsd.org"


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

Re: [RFC] less patches: control the PATH

2017-10-06 Thread Kyle Evans 
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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Getting off topic (Re: portmaster, portupgrade, etc)

2017-10-06 Thread Baptiste Daroussin 
On Fri, Oct 06, 2017 at 01:28:59PM +, George Mitchell wrote:
> On 10/06/17 04:20, Baptiste Daroussin wrote:
> > On Fri, Oct 06, 2017 at 08:13:42AM +, 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 +, 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?
> > 
> > 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 
> > packages
> > 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
> > 
> 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
> 

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


signature.asc
Description: PGP signature

Getting off topic (Re: portmaster, portupgrade, etc)

2017-10-06 Thread George Mitchell 
On 10/06/17 04:20, Baptiste Daroussin wrote:
> On Fri, Oct 06, 2017 at 08:13:42AM +, 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 +, 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?
> 
> 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 
> packages
> 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
> 
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



signature.asc
Description: OpenPGP digital signature

Re: [RFC] less patches: control the PATH

2017-10-06 Thread Guido Falsi 
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 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [RFC] less patches: control the PATH

2017-10-06 Thread Baptiste Daroussin 
On Fri, Oct 06, 2017 at 01:11:46PM +, 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
> 
> 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 :)

renamed BINARY_LINKS which is less worse :)

Best regards,
Bapt


signature.asc
Description: PGP signature

[RFC] less patches: control the PATH

2017-10-06 Thread Baptiste Daroussin 
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


signature.asc
Description: PGP signature

graphics/netpbm update to netpbm-10.80.00

2017-10-06 Thread David Wolfskill 
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
-- 
David H. Wolfskill  da...@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.


signature.asc
Description: PGP signature

First Kempinski 5-star hotel branded residences to launch in Asia from S$7xx,000 onwards.

2017-10-06 Thread KLCC - Property Newsletter 
View online version 
[http://g2wq.mjt.lu/nl2/g2wq/188pn.html?m=AEsAAIEtmPcAAU2lpoAAAGty8HQAARp4FSoAGrBuAAcZrABZ10uZpmhfvmVZQFWW5nyE_EY2FAAGxrU=535ca599=7a88ef2c=G0wm0OECQNb2ARwor9YImfylvSQCW2xWeZVI4sBQ4eU]



[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  registered company that operates various business units, brands 
and associated Intellectual Property under license. These brands include but 
are not limited to BBI or Property Newsletter (PN). You are receiving this 
email as you have previously registered with one of the BBI business units or 
associates.

PN offers marketing services to 3rdparty ("Advertiser(s)") and does not take 
any responsibility for the legality or accuracy of any information provided by 
such Advertisers. The information contained in this message is provided by an 
Advertiser who is aware of the target audience and fully responsible for the 
legality and accuracy of the content provided, no such information forms part 
of any contract. Although every attempt is made to work only with ethical and 
professional Advertisers PN is unable to verify the contents 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 information obtained from any 
of its websites (including PN) or advertising messages such as this.

The information supplied by Advertisers is made available within messages like 
these and, where applicable, on the PN web site solely for the purpose 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 
contents of the information contained in these websites nor does PN accept any 
responsibility for any harm or loss caused by the usage of any information 
contained within these websites or any other website that is linked to the PN 
or BBI  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 under 
the terms and conditions agreed to by the data supplier. Under no circumstances 
will the any personal information be passed to a thirdparty, we regard 
yourprivacy as paramount and can ensure all information will remainprivate.

PN reserves the right to amend the content of this web site at any time without 
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 
invested amount. Such activities is not suitable for everyone. As 
overseasinvestments carry additional financial, regulatory and legal risk, 
investors are advised to do the necessary checks and research on the investment 
beforehand. Past performance not necessarily indicative of future performance. 
T applies.



This e-mail has been sent to po...@freebsd.org, click here to unsubscribe 
[[[UNSUB_LINK_EN]]].
MBFC Tower 3 018974 Singapore SG
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portmaster, portupgrade, etc

2017-10-06 Thread Baptiste Daroussin 
On Thu, Oct 05, 2017 at 10:08:54PM +, 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.
It can... and for a while, the fact it is not used in packaging base is another
subject, but the tool can definitly do it.

[...]
> 
> 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.

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 users to
use binary packages in the first place... Just sating...

Bapt


signature.asc
Description: PGP signature

Re: portmaster, portupgrade, etc

2017-10-06 Thread Mike Clarke 
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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portmaster, portupgrade, etc

2017-10-06 Thread Baptiste Daroussin 
On Fri, Oct 06, 2017 at 08:13:42AM +, 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 +, 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?

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 packages
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


signature.asc
Description: PGP signature

Re: portmaster, portupgrade, etc

2017-10-06 Thread Steve Kargl 
On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote:
> On Wed, Oct 04, 2017 at 05:15:18PM +, 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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2017-10-06 Thread portscout 
Dear port maintainer,

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

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

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


Port| Current version | New version
+-+
devel/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.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portmaster, portupgrade, etc

2017-10-06 Thread Dave Horsfall 

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."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portmaster, portupgrade, etc

2017-10-06 Thread Baptiste Daroussin 
On Wed, Oct 04, 2017 at 05:15:18PM +, 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).

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 account 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 third
party tools that works on the ports tree directly.

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: portmaster, portupgrade, etc

2017-10-06 Thread Matthew Seaman 
On 06/10/2017 00:29, tech-lists wrote:
> 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?

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



signature.asc
Description: OpenPGP digital signature