Matt,
Just mirroring pkgsrc using git is of course fine; actually it's
great, but I wasn't referring to that but rather to those *possible*
future plans of, I quote, "do[ing] some sort of local mod thing in the
future using another branch".
Cheers,
Alex Hornung
I think there's a misunderstanding here. Right now all we are doing
is mirroring the pkgsrc repo. We are mirroring it exactly. We are
not forking or branching anything.
Putting it into a git repo is a convenience to us and our users
because NetBSD's cvs repo is slow and unre
Hi all,
I also agree with Alex.
Maybe we should put more effort in fixing & submitting directly to
upstream, than in branching pkgsrc and having our own fixes in a
separate repo.
Cheers,
Antonio Huete
> While the idea of having a git mirror of pkgsrc is nice, I totally disagree
> with the idea of
Alex Hornung schrieb:
While the idea of having a git mirror of pkgsrc is nice, I totally disagree
with the idea of using it for local modifications.
If we do that, we can just call it a fork directly and no need to call it
pkgsrc anymore.
Also, the solution to getting stuff working isn't keeping
While the idea of having a git mirror of pkgsrc is nice, I totally disagree
with the idea of using it for local modifications.
If we do that, we can just call it a fork directly and no need to call it
pkgsrc anymore.
Also, the solution to getting stuff working isn't keeping local
modifications, bu
We have setup a GIT pkgsrc repo on avalon to give DragonFly users
and developers a more reliable way to track the pkgsrc tree.
git://avalon.dragonflybsd.org/pkgsrc.git
The branch is 'vendor'.
You can fetch from avalon or crater, and soon chlamydia as well.
Crater
