From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] [Fwd: Re: [gentoo-core] Re: [gentoo-dev] dummy-sources]
Date: 26 Jul 2003 09:36:24 -0400 [thread overview]
Message-ID: <1059226584.24876.14.camel@vertigo> (raw)
Here is my message as posted in -core
-----Forwarded Message-----
> From: Chris Gianelloni <wolf31o2@gentoo.org>
> To: vapier@gentoo.org
> Cc: gentoo-core@gentoo.org
> Subject: Re: [gentoo-core] Re: [gentoo-dev] dummy-sources
> Date: 26 Jul 2003 09:30:25 -0400
>
> On Sat, 2003-07-26 at 01:31, Mike Frysinger wrote:
> > PORTDIR_OVERLAY ... but that assumes that the user knows enough to go about
> > developing their own (albeit small) package to do this ...
>
> I think if they know enough to be custom patching their kernel, they can
> create a dummy-sources ebuild. Maybe you could create one up and submit
> it to breakmygentoo.net, rather than adding it to portage. As everyone
> else said, one of two things are going to happen. Either the person is
> going to be patching vanilla-sources, in which case they can have
> vanilla-sources installed, or they're downloading their own kernel, in
> which case, they can create an ebuild in the PORTDIR_OVERLAY. Hell, I
> went and made an ebuild for my custom kernel set, so I don't have to
> hand patch over 100 patches on each of my machines. I simply stuck an
> ebuild in my NFS mounted PORTDIR_OVERLAY and "emerge wolf-sources"... =]
>
> --
> Chris Gianelloni
> Developer, Gentoo Linux
>
>
> --
> gentoo-core@gentoo.org mailing list
>
--
Chris Gianelloni
Developer, Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-07-26 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1059226584.24876.14.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@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