public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Shared libraries in Gentoo
Date: Thu, 9 Sep 2010 02:56:54 +0200	[thread overview]
Message-ID: <20100909005654.GA15206@nibiru.local> (raw)
In-Reply-To: <201009072320.54829.alan.mckinnon@gmail.com>

* Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> > True. But FreeBSD isn't that popular like Windows, Mac or Linux.
> 
> So you don't work at a Tier 1 ISP then?
> 
> FreeBSD rules that space. I get hugely better performance out of Postfix on 
> FreeBSD than on Linux - all other ISPs in this country concur.

Well, not everybody is a tier-1 isp ... ;-o

BTW: one of my customers, a really big one here in Germany
(who also has several of the major free mail portals) runs
its mail systems on GNU/Linux (well, inhouse mailing is done
via Exchange+ADS, surprisingly it actually works ;-)).

But I'd really like to know what produces the performance hits
on Posfix @ Linux.
 
> In fact, portage is complete overkill and I refuse to allow it
> to be deployed at work. Check my posting history for the
> rationale behind this.

Well, portage could be much thinner if certain things would be
moved explicitly out-of-scope or solved more generic on a 
different layer. (yes, I'm explicitly ignoring the historical
issues right now ;-p).

For example:

* distro-specific and various source retrieval methods would not
  be necessary, if the packaging/distro-build system would simply
  fetch it's sources from an vcs (eg. git ;-p) using canonical
  versioning/namespace scheme [1].

* instead of useflags (the terminology implies we're switching
  things some package *uses*, not provides), model the available
  features, eg. like Briegel [2] does. (that's more a methological
  that a technical issue).

* instead of slotting, assign separate package names when multiple
  version concurrency is required (and maybe pull them together
  via virtuals)

* rely on an pure DAG as dependency graph - per definition.
  when circular dependencies occour, fix them in the source tree,
  for example splitting off certain packages in several smaller ones.


[1] http://www.metux.de/download/oss-qm/normalized_repository.pdf
[2] https://sourceforge.net/p/briegel/


Don't get me wrong, that shall not be understood as ranting against
Gentoo, just showing suitable approaches we'd start afresh on a
"green grassland" (w/o all the historical burdens).


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------



  parent reply	other threads:[~2010-09-09  1:09 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 18:28 [gentoo-user] Shared libraries in Gentoo Al
2010-09-06 20:30 ` [gentoo-user] " Nikos Chantziaras
2010-09-06 21:24   ` Al
2010-09-06 21:38     ` Al
2010-09-06 22:49     ` Nikos Chantziaras
2010-09-07  1:00       ` Al
2010-09-09  3:11     ` Enrico Weigelt
2010-09-06 22:43 ` walt
2010-09-07  0:39   ` Al
2010-09-07  3:47     ` Ajai Khattri
2010-09-07  9:33       ` Al
2010-09-07 16:13         ` Ajai Khattri
2010-09-07 16:40           ` Alan McKinnon
2010-09-07 18:15             ` Al
2010-09-07 21:20               ` Alan McKinnon
2010-09-07 23:51                 ` Al
2010-09-08 16:07                 ` Al
2010-09-09  2:36                   ` Enrico Weigelt
2010-09-09  8:55                     ` Al
2010-09-10  1:00                       ` Enrico Weigelt
2010-09-09 10:28                     ` Al
2010-09-09 11:12                       ` [gentoo-user] " Andrea Conti
2010-09-09 12:28                         ` Al
2010-09-10  0:40                         ` Enrico Weigelt
2010-09-10  0:38                       ` [gentoo-user] " Enrico Weigelt
2010-09-09  0:56                 ` Enrico Weigelt [this message]
2010-09-09  8:56                   ` Alan McKinnon
2010-09-09 11:50                     ` Al
2010-09-09 12:25                       ` Alan McKinnon
2010-09-09 13:20                         ` Al
2010-09-09 13:54                           ` Alan McKinnon
2010-09-09 15:12                         ` Neil Bothwick
2010-09-09 15:26                           ` Alan McKinnon
2010-09-09 16:28                             ` Neil Bothwick
2010-09-09 21:03                             ` Graham Murray
2010-09-09 23:49                     ` Enrico Weigelt
2010-09-10 16:43                       ` Florian Philipp
2010-09-10 19:02                         ` Alan McKinnon
2010-09-10 23:25                         ` walt
2010-09-09  2:52               ` Enrico Weigelt
2010-09-09 15:02                 ` Al
2010-09-10  0:19                   ` Enrico Weigelt
2010-09-10 12:27                     ` Al
2010-09-12 21:30                       ` Enrico Weigelt
2010-09-12 22:47                         ` Al
2010-09-13  1:11                           ` Enrico Weigelt
2010-09-07 19:12           ` Al
2010-09-08 19:29   ` Al

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=20100909005654.GA15206@nibiru.local \
    --to=weigelt@metux.de \
    --cc=gentoo-user@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