public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: EBo <ebo@sandien.com>
To: <gentoo-soc@lists.gentoo.org>
Subject: Re: [gentoo-soc] Application for Google Summer of Code 2018-Mishal  Roy
Date: Fri, 23 Mar 2018 07:49:29 -0600	[thread overview]
Message-ID: <a9c0f549b7db0192a74878c8c619f5ed@mail.swcp.com> (raw)
In-Reply-To: <CAGfcS_n6npsCE7zERfg_urpVyYRRN73FhkX3wQ22kU705OxCfQ@mail.gmail.com>

On Mar 23 2018 7:37 AM, Rich Freeman wrote:
> On Fri, Mar 23, 2018 at 2:50 AM, Patrick Lauer <patrick@gentoo.org> 
> wrote:
>>
>> https://github.com/adjust/gentoo-overlay/tree/master/sys-kernel
>>
>> This just needs to be cleaned up a bit to be upstreamed, and so far 
>> I've
>> not had the time for it.
>>
>> It's a solved problem (I'm aware of at least two other ebuilds to do 
>> the
>> same) :)
>>
>
> Yeah, that is certainly one approach.  Part of me thinks that
> modularizing the initramfs portion would be ideal, and as Benda
> suggested making it possible to install the built sources might be
> useful (if doing so one would need to patch the file that points to
> the build location so that future module builds can find them).  This
> particular ebuild uses sources in /usr/src but I think it would be
> cleaner to just fetch these into the build directory.
>
> The package I find most frustrating is zfs-kmod, because it needs
> fully-built sources and not just prepared sources.  I build to a
> tmpfs, and re-creating prepared sources using that approach is
> trivial, but doing a full rebuild just to update zfs modules is a bit
> painful (granted, less so now that I have 12 cores).  I've been too
> lazy to figure out why zfs needs them...

In the past I have had zfs-kmod seriously break my kernel builds.  
Cleaning that up to be consistent would probably be useful to the 
general community as a whole IMNSHO.  Isn't there a way to set the build 
and install directories from some env variable?  If so, maybe verifying 
that the core emuilds are consistent would be helpful.  Hmmm... in the 
past I have written utility scripts to check for things like this.  
Would it be reasonable to add those checks to repoman (or whatever it is 
called today)?

Hope I am not out of line asking this on this forum.

   EBo --


  reply	other threads:[~2018-03-23 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 17:51 [gentoo-soc] Application for Google Summer of Code 2018-Mishal Roy Mishal Roy
2018-03-22  4:07 ` Benda Xu
2018-03-22 15:16   ` Mishal Roy
2018-03-23  0:47     ` Benda Xu
2018-03-22 15:25   ` Rich Freeman
2018-03-22 16:06     ` Mishal Roy
2018-03-23  3:33     ` [gentoo-soc] kernel ebuild (Was: Application for Google Summer of Code 2018-Mishal Roy) Benda Xu
2018-03-23  6:50     ` [gentoo-soc] Application for Google Summer of Code 2018-Mishal Roy Patrick Lauer
2018-03-23 13:37       ` Rich Freeman
2018-03-23 13:49         ` EBo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-16  5:16 Mishal Roy
2018-03-17 22:50 ` Benda Xu

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=a9c0f549b7db0192a74878c8c619f5ed@mail.swcp.com \
    --to=ebo@sandien.com \
    --cc=gentoo-soc@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