From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 14 18:50:36 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26A381065670 for ; Wed, 14 Apr 2010 18:50:36 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC6D18FC13 for ; Wed, 14 Apr 2010 18:50:35 +0000 (UTC) Received: by pwi9 with SMTP id 9so455189pwi.13 for ; Wed, 14 Apr 2010 11:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=SVuNtQP8SUDa2hdGeiN98gzqOh6eoLBpXgf/O5XMYBg=; b=hlwkPMw4KhXQLgpvX92/og8LunXyl1871CYch12vgqkGZPwhWMbqlIoy841a8fLrqV fgg9XZ78K2V15brqN2Be+691MZTJyf5hlsb3WC9P3rUNBxtAaQqi4wogXJkFzUqMgG9j No4wPfW2WkJkJG1yVlBCRLmRH68/7ZkvKObyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=UxJ3fYstzCW5XP9BMtyFifSH8iN/mZQBKJhyyDjTCER8EU6NGsgwNb+tO5D7reBcrs pFnNY7KrQUUT0fhcpCZCaEemchwrxYleXLK+B0wqY3cKzg/jTbjrdlAroB0mZMDCOF9f hybOb1qSpEYYlcMvYViWvC6TBoH2cWZZw5CKQ= MIME-Version: 1.0 Received: by 10.231.14.76 with HTTP; Wed, 14 Apr 2010 11:50:35 -0700 (PDT) In-Reply-To: References: <20100414174853.GC43908@dan.emsphone.com> Date: Wed, 14 Apr 2010 11:50:35 -0700 Received: by 10.140.247.5 with SMTP id u5mr7799799rvh.62.1271271035414; Wed, 14 Apr 2010 11:50:35 -0700 (PDT) Message-ID: From: Freddie Cash To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: there is a way to avoid strict libraries linking? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2010 18:50:36 -0000 On Wed, Apr 14, 2010 at 11:18 AM, Leinier Cruz Salfran < salfrancl.listas@gmail.com> wrote: > On Wed, Apr 14, 2010 at 1:48 PM, Dan Nelson > wrote:> Just because you > > Anyway, the FreeBSD port maintainers usually bump the > > revision of dependant ports when a major library like libpng gets > upgraded, > > to force everyone to upgrade anything that depends on it. > > > > mmm .. I think it's not true because I maintain a port and i'm VERY > VERY restricted to update the port because I depends on a mentor that > will ONLY update the port in fbsd svn tree if I sent to him the > tinderbox log of the sucessfully build of the port .. so I have not > much patience to do all this things so I update the port and do ALL > task including constructing the package into tinderbox ONLY when a new > version of the program is available .. and I think that exists a lot > of ports maintainers that are in same situation > > do you agree with me that it's difficult to a port maintainer to > update his/her port because of this restriction???? > The port maintainer doesn't *have to* update anything. When library ports go through a library bump like this, all the ports that depend on it get an automatic PORTREVISION bump. All the port maintainer has to do is double-check that the port compiles with the new version of the lib. Only if there are issues with that (which usually get picked up by the -exp runs on the ports cluster), then the port maintainer has to step in and fix things. 9 times out of 10, a port maintainer doesn't have to do anything with a port until a new version of the app is released. > could be a good idea to plan and implement a system to allow fbsd > ports maintainers to maintain easyly the own ports via web or mail > ONCE a fbsd mentor have uploaded his/her port to fbsd svn > tree???????????? > In several years of port maintainership, I've never had a need for anything like this. A new version of an app I maintain is released, I update the port locally, test it, submit a PR with the update, someone looks at it and sends back suggestions/issues, the port is fixed locally and patches re-submitted to the PR, and then the port is committed to the tree. Overall, not a long process. If you maintain enough ports for enough time, and generate enough committed PRs to annoy people enough, you get rewarded with a commit bit. :) -- Freddie Cash fjwcash@gmail.com