From: A Schenck <lane_andrew@hotmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Week 6 Report for Big Data Infrastructure and H2O ebuilds Project
Date: Tue, 20 Jul 2021 10:39:09 -0700 [thread overview]
Message-ID: <DM6PR07MB41567B1C5031BD2ABC013A399DE29@DM6PR07MB4156.namprd07.prod.outlook.com> (raw)
In-Reply-To: <CACk4dkvsuNt4s+iHJQsmbwyxi_R8S785bPYrO5vrprGt4uVMfw@mail.gmail.com>
On 7/18/21 10:52 PM, Yuan Liao (Leo) wrote:
> Hi folks,
>
> <snip/>
>
> As per my original project proposal, I am also adding a test case for
> the ebuild installation tests which will ensure every package in the
> Spark overlay can be installed at least once. Adding every package to
> the emerge command theoretically works, but the command would be too
> long. Invoking emerge separately for each package would resolve this
> problem, but the overhead of emerge's dependency calculation would
> seriously impact the test runtime. I came up with a solution that
> could address both issues: write a script to compute a list of leaf
> packages in the Spark overlay and pass the packages in the list to
> emerge, so every package in the overlay would be installed, and the
> emerge command can be simplified to have a shorter length too. The
> script can also act as a helpful tool for any ebuild repository's
> maintainers to find out all leaf packages in the repository for
> maintenance tasks like last-rite and package clean-up. After some
> initial optimization and tuning, the script (written in Python) can
> compute a list of leaf packages among about 500 packages in the Spark
> overlay within only a few minutes. The optimization and tuning is
> also the topic for this week's blog post of mine [1]. This post
> covers some knowledge and topics from computer science, including
> graph theory, graph algorithms, data structure, and time complexity.
> If you are interested in any of those subjects, make sure you don't
> miss it!
Thanks! We actually don't really care much about Java (haven't used it
seriously since College), and haven't even been involved in Gentoo GSoC
in a decade, but we're glad we stay on this list for things like this.
It's really nice seeing someone who still has that spark of interest in
computer things. We do happen to like graph theory and network analysis
and time complexity and such, but haven't really been able to apply it
in "the real world" of tech companies. Every time we try to do things
"the right way" with real computer science, coworkers and bosses just
say "just hack something together".
Oh well, thanks for what you're doing,
-A
>
> <snip/>
>
> This concludes my work during the past week and this report. Thank
> you for reading it (and my blog post in case you are checking it out)!
>
> Best regards,
> Leo
>
> [1]: https://leo3418.github.io/2021/07/18/find-leaf-packages.html
> [2]: https://wiki.gentoo.org/wiki/User:Leo3418/Kotlin/Package_Maintainer_Guide
>
next prev parent reply other threads:[~2021-07-20 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 5:52 [gentoo-soc] Week 6 Report for Big Data Infrastructure and H2O ebuilds Project Yuan Liao (Leo)
2021-07-19 10:29 ` Benda Xu
2021-07-20 17:39 ` A Schenck [this message]
2021-07-21 6:23 ` Yuan Liao (Leo)
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=DM6PR07MB41567B1C5031BD2ABC013A399DE29@DM6PR07MB4156.namprd07.prod.outlook.com \
--to=lane_andrew@hotmail.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