From: Grobian <grobian@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Re: Prefix tree locaiton
Date: Thu, 17 Aug 2006 21:18:04 +0200 [thread overview]
Message-ID: <20060817191804.GA23764@gentoo.org> (raw)
In-Reply-To: <411BFE87-2CBC-4E30-A46C-E4BB233F7B4A@goodship.net>
On 17-08-2006 13:25:14 -0400, Armando Di Cianno wrote:
Armando!!!!!!!!!!
(you don't know me, but I DO feel aquintanced with you, hahahaha ...
GNUstep)
> Hi, all. I've just subscribed to the list, after chatting with
> people on #gentoo-osx. I'm *fervently* excited about getting portage-
> prefix on gentoo-osx to a stable level. IMHO, fink has had it's
> glory days, and darwinports seems both stable, and incredibly
> terrible at the same time.
Aham...
> > So, not being too much familiar with the plethora of VCSes around
> > and their capabilities, do you have an idea of how you can easily
> > pull the svn tree and keep your own changes in there, submitting
> > patches every now and then to include them on the main tree?
>
> If you have a local svn trunk that looks like
> trunk/Adir
> trunk/Bdir
> trunk/Cdir
> then you can do something like the following:
> cd trunk
> svn propedit svn:externals A
> (editor opens)
> dir-name-that-will-be-created-in-Adir svn://gentoo.org/svn/portage/
> trunk
> (save, close editor)
> svn update
> ls Adir
> ./Adir/dir-name-that-will-be-created-in-Adir
> ... and the code in that external trunk will be in that named
> directory inside Adir.
Heu... ehm. Ok, I guess this shows it can easily be done with svn, so
that's great!
> What this /doesn't/ let you do is commit back to the external (unless
> you actually had authenticated access). But, gratuitous use of svn
> diff could be used to submit patches.
Of course. In CVS I can imagine that CVS just merges all updates all
the time. With git I know you can have your own local commits, so my
idea was basically like this. Not ideal for non-gentoo devs, but I
think that's the easiest way for now to get the work contributed and in
the main tree.
> Conceivably, this method could also be used to host a prefix-enabled
> portage ebuild tree, that we /could/ submit back to, and then
> "official" devs could update the diffs themselves.
In the spirit of the much criticised Sunrise, I wouldn't really "care"
if someone set up a central repo where non-devs commit their stuff in,
and that I periodically pull over all changes. I have the bandwith
available to host it myself (would make it even easier to do the sync I
suppose) but not the machine at the moment. (Need to do a lot of
painting etc. anyway too, so I can't set it up soon.)
I'd be very very very happy if we could get some movement here, so if
you folks can start, please do! I will help wherever that is possible.
--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-17 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 17:25 [gentoo-osx] Re: Prefix tree locaiton Armando Di Cianno
2006-08-17 19:18 ` Grobian [this message]
2006-08-17 20:05 ` Christopher Chan
2006-08-18 15:43 ` Armando Di Cianno
2006-08-18 15:56 ` Grobian
2006-08-18 16:03 ` Armando Di Cianno
2006-08-24 20:19 ` Grobian
2006-08-25 20:50 ` Christopher Chan
2006-08-26 8:03 ` Grobian
2006-09-06 9:20 ` Grobian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060817191804.GA23764@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-osx@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox