Hi,
2010/10/20 Matthew Dillon :
> Ok, I think the git repo is synced up now and the new script will
> keep it that way with fixup commits when fromcvs/togit miss
> something.
>
> -Matt
I have just finished pkg_rolling-replace perfectly.
Than
Ok, I think the git repo is synced up now and the new script will
keep it that way with fixup commits when fromcvs/togit miss
something.
-Matt
On Tue, October 19, 2010 1:31 pm, Matthew Dillon wrote:
> I disagree. The reason why BSD's are marginal platforms relative to
> third party software is because third party software is developed for
> linux and not for the BSDs, and despite the configure-from-hell that
> they all u
:The idea shouldn't be to get everything into pkgsrc proper, but to get
:changes into upstreams proper. In fact I personally think that the ease
:of committing local patches into the pkgsrc/ports/etc trees is the main
:factor why BSD's are so marginal platforms in the eyes of the developers
:of th
:On 18.10.10 23:33, Matthew Dillon wrote:
:> Hmm. It looks like a CVS dollar expansion issue. The patch itself
:> is just fine but the CVS dollar expansion doesn't get mirrored
:> properly because it isn't actually in the cvs repo (it's adjusted on
:> checkout).
:
:When calculatin
On 18.10.10 8:45, Matthew Dillon wrote:
> Of course, the idea is to get everything into pkgsrc proper but having
> a local branch will give us the ability to consolidate and maintain
> patches that haven't yet gotten to pkgsrc proper.
The idea shouldn't be to get everything into pkgsrc proper, but
On 18.10.10 23:33, Matthew Dillon wrote:
> Hmm. It looks like a CVS dollar expansion issue. The patch itself
> is just fine but the CVS dollar expansion doesn't get mirrored
> properly because it isn't actually in the cvs repo (it's adjusted on
> checkout).
When calculating check
On Mon, October 18, 2010 8:33 pm, Samuel J. Greear wrote:
>>If we are going to do this, NOW is the time. Comments?
>
> As you already know, I am for this. I don't think auto-merging is
> strictly necessary. It is certainly worth a try, we can cross our
> fingers and hope it just works, but I t
:
:I'm using master branch of pkgsrcv2 and 'git show 31' says 'Update
:"apr-util" package to version 1.3.10', but Makefile haven't changed
:(1.3.9nb2).
:
:pkgsrc-2010Q2 branch have Makefile updated to 1.3.10 and 'git show
:ff920fb' says patch-ab have removed, but the patch still exists.
:
:It
Hi,
2010/10/19 Matthew Dillon :
> Ok, this may take a while. The basic problem is that a number of
> patch files in pkgsrc didn't follow the pkgsrc rules on making patch
> files and ended up with $NetBSD$ expansions that don't match what
> was committed to cvs. There is no easy solut
>If we are going to do this, NOW is the time. Comments?
As you already know, I am for this. I don't think auto-merging is
strictly necessary. It is certainly worth a try, we can cross our
fingers and hope it just works, but I think the real benefit will be
having a large/working/stable set of
Matthew Dillon wrote:
If we are going to do this, NOW is the time. Comments?
comments: "yay!"
as much as I was *against* git to start with for big projects -
I am now a convert - it kind of formalizes all of the traditional
'patches floating around' unix culture -
and you can still centra
Ok, this may take a while. The basic problem is that a number of
patch files in pkgsrc didn't follow the pkgsrc rules on making patch
files and ended up with $NetBSD$ expansions that don't match what
was committed to cvs. There is no easy solution from the git repo
side becaus
:I have a problem with devel/apr-util. It seems commit
:3176873f464fae2973d431bbf236e8b5bc24 missing some diffs.
:It should be version 1.3.10 ( http://pkgsrc.se/devel/apr-util )
:
:# cd /usr/pkgsrc/devel/apr-utl
:# bmake
:=> Bootstrap dependency digest>=20010302: found digest-20080510
:===> Pa
Hi,
>The status on our pkgsrc mirror is that it appears to be fairly stable.
>It has been slurping the updates from NetBSD on a 6-hour interval with
>no problems.
I have a problem with devel/apr-util. It seems commit
3176873f464fae2973d431bbf236e8b5bc24 missing some diffs.
It shou
> For whatever it's worth, here are the patches: http://bit.ly/dCrm4t
>
> Note that there are some quirks (such as the konsole title being messed
> up when connecting with ssh from konsole), but it generally works quite
> well with those patches.
Thanks Alex, you are very helpful. Getting the pat
On 10/18/2010 9:14, Francois Tigeot wrote:
The maintainer has been set dfly-pkg-people. I hoped there was some sort of
local team behind this address.
As Hasso said earlier, setting up more involvement of DragonFly people
in the pkgsrc team is being worked on.
Sascha
On 18/10/10 06:53, Alex Hornung wrote:
> On 18/10/10 00:32, elekktrett...@exemail.com.au wrote:
>> Can we please get KDE 4 to some sort of semi-usable state? There has been
>> patches(process states) waiting to get in pkgsrc(i think from Hasso?) for
>> about a year now, but I remember with KDE work
On Sun, Oct 17, 2010 at 07:11:27PM -0400, Justin C. Sherrill wrote:
> On Sun, October 17, 2010 4:24 pm, Francois Tigeot wrote:
> > On Sun, Oct 17, 2010 at 12:21:24PM -0700, Matthew Dillon wrote:
> >>
> >> :
> >> :The 2010Q3 release of pkgsrc has been branched - how close are we to
> >> :branching D
On 18/10/10 00:32, elekktrett...@exemail.com.au wrote:
> Can we please get KDE 4 to some sort of semi-usable state? There has been
> patches(process states) waiting to get in pkgsrc(i think from Hasso?) for
> about a year now, but I remember with KDE workspace/base >= 4.4 there has
> been other iss
One more thing I will note. If we create a local dragonfly branch
for pkgsrc stuff then all dragonfly committers will be able to commit
into it and, theoretically, could serve as a reference point for sending
requests to the main pkgsrc list (a convenient URL to get the changes),
:> :The 2010Q3 release of pkgsrc has been branched - how close are we to
:> :branching DragonFly 2.8? I'd like to get both building for the pkgsrc
:> :binaries.
:
:Can we please get KDE 4 to some sort of semi-usable state? There has been
:patches(process states) waiting to get in pkgsrc(i think f
> :The 2010Q3 release of pkgsrc has been branched - how close are we to
> :branching DragonFly 2.8? I'd like to get both building for the pkgsrc
> :binaries.
Can we please get KDE 4 to some sort of semi-usable state? There has been
patches(process states) waiting to get in pkgsrc(i think from Has
On Sun, October 17, 2010 4:24 pm, Francois Tigeot wrote:
> On Sun, Oct 17, 2010 at 12:21:24PM -0700, Matthew Dillon wrote:
>>
>> :
>> :The 2010Q3 release of pkgsrc has been branched - how close are we to
>> :branching DragonFly 2.8? I'd like to get both building for the pkgsrc
>> :binaries.
>>
>>
On Sun, Oct 17, 2010 at 12:21:24PM -0700, Matthew Dillon wrote:
>
> :
> :The 2010Q3 release of pkgsrc has been branched - how close are we to
> :branching DragonFly 2.8? I'd like to get both building for the pkgsrc
> :binaries.
>
> I will branch 2.8.0 this evening. We will bump it to 2.8.1
:
:The 2010Q3 release of pkgsrc has been branched - how close are we to
:branching DragonFly 2.8? I'd like to get both building for the pkgsrc
:binaries.
I will branch 2.8.0 this evening. We will bump it to 2.8.1 and
resync from master when we actually release (if we actually
releas
The 2010Q3 release of pkgsrc has been branched - how close are we to
branching DragonFly 2.8? I'd like to get both building for the pkgsrc
binaries.
27 matches
Mail list logo
