Re: Maintaining mono/.net

On Tue, Jun 28, 2016 at 2:43 AM, Baptiste Daroussin wrote: > On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: >> Hello Ports Team, >> >> A couple of us on the freebsd-mono@ mailing list are having a >> discussion on how best to maintain the mono ports/.net ports.

Re: best way to tune ports to add a CLFAGS entry

On Wed, 29 Jun 2016 00:52:51 +0800 Julian Elischer wrote > At work I am doing various cross compiles in order to make a product > under freebsd that actually will run under a modified FreeBSD that > runs on an appliance. We want to get away from hand rolling everything >

Re: Is there still broken lang/ruby23 ?

Yes, I haven't looked at it yet, but if you want to take a look, I'd welcome patches. Steve On 06/28/16 06:12 PM, KIRIYAMA Kazuhiko wrote: > Hi, > > Is there still broken lang/ruby23[1]. Or can build in latest > 11.0-* ? > > [1]

Re: Unexpected output from "pkg updating -d 20160626"

On Tue, Jun 28, 2016 at 09:19:04PM -0400, Jason Unovitch wrote: > ... > > The "pkg updating" command I issued was: pkg updating -d 20160626 > > Hello David, > I did replicate this and it seemed related to a handful of recent > UDPATING entries that were made without a trailing colon after the

Re: Unexpected output from "pkg updating -d 20160626"

On Tue, Jun 28, 2016 at 04:44:33AM -0700, David Wolfskill wrote: > As part of my daily update of FreeBSD on my laptop, on the first reboot > after installing the freshly-built kernel & world, I use portmaster to > update any installed ports that have been updated since I last updated. > > This

Re: best way to tune ports to add a CLFAGS entry

On 6/28/16 9:52 AM, Julian Elischer wrote: At work I am doing various cross compiles in order to make a product under freebsd that actually will run under a modified FreeBSD that runs on an appliance. We want to get away from hand rolling everything to leverage all teh work in getting ports

Is there still broken lang/ruby23 ?

Hi, Is there still broken lang/ruby23[1]. Or can build in latest 11.0-* ? [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 --- KIRIYAMA Kazuhiko ___ freebsd-ports@freebsd.org mailing list

Re: blanket portmgr approval vs. non-fixing changes

On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: > Am 28.06.2016 um 11:17 schrieb Baptiste Daroussin: > > > What you are asking is part of the blanket in particular when changing > > things in > > individual ports, we expect committers to have a look at pending PR (yes I > >

Re: blanket portmgr approval vs. non-fixing changes

Am 28.06.2016 um 11:17 schrieb Baptiste Daroussin: > What you are asking is part of the blanket in particular when changing things > in > individual ports, we expect committers to have a look at pending PR (yes I > know > I have been guilty of individual port change without sometime checking

Re: blanket portmgr approval vs. non-fixing changes

Am 27.06.2016 um 18:07 schrieb Cy Schubert: > Mathias, Cy, Mind the double t please. > I'm surprised at your position. I recall a commit you made to one of my > ports a few years ago, to which I objected. Your position now is a complete > reversal of your arguments then. Quite possible.

Re: blanket portmgr approval vs. non-fixing changes

Am 27.06.2016 um 12:02 schrieb Guido Falsi: >> 2. What I was meaning to state was that (and I'll not pick at the >> kind soul who has modernized the port) we should only apply the >> blanket approval if ports have fallen into disrepair. > > I'd say that it's a matter of urgency for the change.

Re: pkg SAT_SOLVER bugs

On 06/28/16 00:09, Baptiste Daroussin wrote: On Mon, Jun 27, 2016 at 11:42:08PM +0200, Rodrigo OSORIO wrote: On 06/27/16 12:38, Hans Petter Selasky wrote: Hi, I found some bugs in PKG with regard to the SAT_SOLVER environment variable. Please find patch attached :-) Issues fixed: 1) No need

Independence Day Sale, starts right now.

This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text emails. You can read the original version online: http://ymlp48.com/zFdEBC

Re: 2016Q2 - no Mk/Uses/mysql.mk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2016-06-28 16:58, Mathieu Arnold wrote: > +--On 28 juin 2016 10:30:10 -0400 Dan Langille wrote: > |> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: > |> > |> > |> > |> +--On 27 juin 2016 17:22:56 -0400 Dan

best way to tune ports to add a CLFAGS entry

At work I am doing various cross compiles in order to make a product under freebsd that actually will run under a modified FreeBSD that runs on an appliance. We want to get away from hand rolling everything to leverage all teh work in getting ports working well on FreeBSD. We have some extra

Re: blanket portmgr approval vs. non-fixing changes

On 28/06/2016 9:03 PM, Alphons van Werven wrote: > Maintainers are already notified by e-mail of commits resulting from PRs > because they are put on the CC list. Maybe it's just me, but I think it > would be very nice if maintainers were *always* automagically notified of > *any* commits to their

Re: pkg SAT_SOLVER bugs

On Tue, Jun 28, 2016 at 05:52:32PM +0200, Hans Petter Selasky wrote: > On 06/27/16 13:55, Baptiste Daroussin wrote: > > On Mon, Jun 27, 2016 at 12:38:02PM +0200, Hans Petter Selasky wrote: > > > Hi, > > > > > > I found some bugs in PKG with regard to the SAT_SOLVER environment > > > variable. >

Re: pkg SAT_SOLVER bugs

On 27/06/2016 8:38 PM, Hans Petter Selasky wrote: > Hi, > > I found some bugs in PKG with regard to the SAT_SOLVER environment > variable. Please find patch attached :-) > > Issues fixed: > 1) No need to use hash table when generating SAT rules for external > solver. Variables are already in a

Re: pkg SAT_SOLVER bugs

On 06/27/16 13:55, Baptiste Daroussin wrote: On Mon, Jun 27, 2016 at 12:38:02PM +0200, Hans Petter Selasky wrote: Hi, I found some bugs in PKG with regard to the SAT_SOLVER environment variable. Please find patch attached :-) Issues fixed: 1) No need to use hash table when generating SAT

Re: 2016Q2 - no Mk/Uses/mysql.mk

+--On 28 juin 2016 10:30:10 -0400 Dan Langille wrote: |> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: |> |> |> |> +--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: |> | I've been working with the 2016Q2 branch with respect to

Re: 2016Q2 - no Mk/Uses/mysql.mk

> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: > > > > +--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: > | I've been working with the 2016Q2 branch with respect to FreshPorts. > | > | I tried running make -V on branches/2016Q2 and it failed

Re: 2016Q2 - no Mk/Uses/mysql.mk

+--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: | I've been working with the 2016Q2 branch with respect to FreshPorts. | | I tried running make -V on branches/2016Q2 and it failed with: | | Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" | line

Unexpected output from "pkg updating -d 20160626"

As part of my daily update of FreeBSD on my laptop, on the first reboot after installing the freshly-built kernel & world, I use portmaster to update any installed ports that have been updated since I last updated. This morning, for the first time in ... months, I think, the "pkg updating -d ..."

Re: blanket portmgr approval vs. non-fixing changes

Kevin Golding wrote: > and about the same time someone did a blanket update of RUN_DEPENDS in > my ports. Including a PORTREVISION bump. It's easy to argue that's a > very trivial change that doesn't needs maintainer involvement, but it > also impacted my day. [snip] > Had I known about the

Re: How to change repository name of installed packages in local database?

Baptiste Daroussin wrote on 06/28/2016 12:33: On Tue, Jun 28, 2016 at 12:16:17PM +0200, Miroslav Lachman wrote: I searched the man pages but cannot find the answer. If we have machine with packages installed from more than one repository and one day we want to use some already installed

Re: How to change repository name of installed packages in local database?

On Tue, Jun 28, 2016 at 12:16:17PM +0200, Miroslav Lachman wrote: > I searched the man pages but cannot find the answer. > If we have machine with packages installed from more than one repository and > one day we want to use some already installed packages from another > repository, is there any

Re: How to change repository name of installed packages in local database?

> On 28 Jun 2016, at 12:16 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > Now we need to switch all packages from testing repo "redmine320" to > production repo "codelab". # pkg annotate -A ${PKG} repository ${REPO} Cheers, Franco ___

How to change repository name of installed packages in local database?

I searched the man pages but cannot find the answer. If we have machine with packages installed from more than one repository and one day we want to use some already installed packages from another repository, is there any easy way of switching this packages to another repo? I am looking for

Re: Maintaining mono/.net

On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: > Hello Ports Team, > > A couple of us on the freebsd-mono@ mailing list are having a > discussion on how best to maintain the mono ports/.net ports. One of > the things that has come up is maintaining the patches for "all this >

Re: blanket portmgr approval vs. non-fixing changes

On Tue, Jun 28, 2016 at 09:12:46AM +0100, Kevin Golding wrote: > On Mon, 27 Jun 2016 21:21:31 +0100, Cy Schubert > wrote: > > > In message <57716d89.1050...@sorbs.net>, Michelle Sullivan writes: > > > > Don't forget that many people see their name/email in the

Re: blanket portmgr approval vs. non-fixing changes

On Mon, 27 Jun 2016 21:21:31 +0100, Cy Schubert wrote: In message <57716d89.1050...@sorbs.net>, Michelle Sullivan writes: Don't forget that many people see their name/email in the maintainer line as being responsible for the port.. so someone goes makes blanket

Re: Maintaining mono/.net

On 06/27/2016 20:21, Kurt Jaeger napisa: Hi! A couple of us on the freebsd-mono@ mailing list are having a discussion on how best to maintain the mono ports/.net ports. One of the things that has come up is maintaining the patches for "all this stuff". The current paradigm in FreeBSD as I

Re: Latest MonoDevelop Progress

On 06/27/2016 18:10, Russell Haley napisa: ... patches, instead of doing it through svn patches. It will make everything WAY easier to push back upstream. Not that it matters, eh, Ivan? :0) I already see who is to be in charge of pushing everything upstream :-P