From: Vikraman Choudhury <vikraman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] New research: Gentoo Portage Package Dependencies
Date: Tue, 20 May 2014 06:38:48 +0530 [thread overview]
Message-ID: <87d2f9z273.fsf@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kY3jHgTxaYyZRe7Oix9mNeU6aDQpukxSmpza-4Y1sktg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Rich Freeman <rich0@gentoo.org> writes:
> On Mon, May 19, 2014 at 6:24 AM, Pavlos Ratis <dastergon@gentoo.org> wrote:
>> Recently I found that there's a new research on Gentoo, specifically
>> for Portage and package dependencies[1].
>
> Thanks for pointing this out! Anybody know anything about their first
> reference, also from 2014? As far as I can tell it hasn't been
> published yet but I figured I'd ask here before I go bugging the
> authors.
>
I found this after googling:
http://essay.utwente.nl/61920/1/Remco_Bloemen_-_Innovation_Dynamics_in_Open_Source_Software.pdf
It is a more interesting read compared to the paper.
> Interesting that they picked Gentoo. It might just be from
> familiarity, but a reason to use Gentoo is that the dependency info
> for a package is separated from the actual distfiles/etc. Many other
> package formats combine these, though perhaps this data is cached
> somewhere in a format that could be used historically. If they had
> multiple GB of ebuild files I'd hate to think about what that would
> look like as .debs.
>
> Rich
--
Vikraman
[-- Attachment #2: Type: application/pgp-signature, Size: 359 bytes --]
next prev parent reply other threads:[~2014-05-20 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 10:24 [gentoo-project] New research: Gentoo Portage Package Dependencies Pavlos Ratis
2014-05-19 18:06 ` Rich Freeman
2014-05-20 1:08 ` Vikraman Choudhury [this message]
2014-05-20 0:02 ` Patrick Lauer
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=87d2f9z273.fsf@gentoo.org \
--to=vikraman@gentoo.org \
--cc=gentoo-project@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