public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs
Date: Fri, 19 Aug 2005 05:30:42 +0200	[thread overview]
Message-ID: <200508190530.46642.trapni@gentoo.org> (raw)
In-Reply-To: <1124379852.21223.161.camel@cgianelloni.nuvox.net>

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]

On Thursday 18 August 2005 17:44, Chris Gianelloni wrote:
> On Thu, 2005-08-18 at 10:17 -0500, Brian Harring wrote:
> > 2) ebuild maintenance will be a nightmare- every new version will
> >    require again walking the source to see if the lines you've drawn for
> >    dividing the source are still proper.

minimize the duplication by a mysql eclass, just like we do for apache e.g. 
(and lots of others) that prevent us from code duplication.

> I'd see no problem with this in mysql, if, for example, mysql's Makefile
> had a "make libmysqlclient" target.  In that case, I would make it a
> separate package. 

Having a look at the already provided libmysqlclient ebuild [1] it obviousely 
(and for our luck) looks like upstream supports this installation types.

> This would also mean a lot of work on your part, as 
> every single package that had a dependency on mysql would now need some
> way of specifying whether the server was going to be local or remote, to
> properly *DEPEND on the correct package.

We've plenty of tools that help us in searching for all ebuilds *directly* 
depending on "dev-db/mysql"; than you just need to decide, wether this needs 
the server or not. And (w/o looking at them) I do predict, that 100% of them 
will only need libmysqlclient.

Why? What package would depend on the server in particular? If the user wants 
the server to be run on localhost, than he would just have to add it to his 
emerge args as well. I see no problems there - instead: it would be a great 
enheancement. (IMO)

> All in all, I think it isn't worth even attempting at this time.

read above. do you still think so? If so, why?

Regards,
Christian Parpart.

[1] http://bugs.gentoo.org/attachment.cgi?id=55816

-- 
 04:43:52 up 148 days, 17:51,  1 user,  load average: 0.66, 0.76, 1.15

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-19  2:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 14:28 [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Christian Parpart
2005-08-18 14:23 ` Luca Barbato
2005-08-18 15:24   ` Francesco R
2005-08-18 14:27 ` Brian Jackson
2005-08-18 14:40 ` Mike Frysinger
2005-08-18 15:13   ` Lance Albertson
2005-08-18 15:24     ` Ciaran McCreesh
2005-08-18 15:28     ` Francesco R
2005-08-18 15:37     ` Chris Gianelloni
2005-08-18 15:56       ` Brian Harring
2005-08-18 16:08         ` [gentoo-dev] Local USE defaults Donnie Berkholz
2005-08-18 16:31           ` Brian Harring
2005-08-18 17:16             ` Alec Warner
2005-08-18 17:36               ` Brian Harring
2005-08-18 17:18             ` Mike Frysinger
2005-08-18 17:38               ` Brian Harring
2005-08-19  7:10                 ` Donnie Berkholz
2005-08-19 11:53                   ` Brian Harring
2005-08-18 17:24         ` [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Ciaran McCreesh
2005-08-18 18:13           ` Brian Harring
2005-08-19  0:06             ` Ciaran McCreesh
2005-08-19  1:59               ` Brian Harring
2005-08-18 15:17 ` Brian Harring
2005-08-18 15:44   ` Chris Gianelloni
2005-08-19  3:30     ` Christian Parpart [this message]
2005-08-19  3:09       ` Brian Harring
2005-08-18 17:01 ` Georgi Georgiev
2005-08-19  2:59   ` Luke-Jr
2005-08-19  5:01     ` Georgi Georgiev
2005-08-19  3:19   ` Christian Parpart

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=200508190530.46642.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --cc=gentoo-dev@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