From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 14 19:02:02 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 E68CB1065679 for ; Wed, 14 Apr 2010 19:02:01 +0000 (UTC) (envelope-from salfrancl.listas@gmail.com) Received: from mail-bw0-f214.google.com (mail-bw0-f214.google.com [209.85.218.214]) by mx1.freebsd.org (Postfix) with ESMTP id 70C8C8FC1F for ; Wed, 14 Apr 2010 19:02:01 +0000 (UTC) Received: by mail-bw0-f214.google.com with SMTP id 6so476738bwz.13 for ; Wed, 14 Apr 2010 12:02:01 -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 :content-transfer-encoding; bh=2/p57Oj9DLwbZNkjcXUEbfRYQoe7jZaxA5uVqIsRRos=; b=BwRmW38tnBaYpx5clVct3+2mPtt+22M7v/Cxq/tbN7mzyEwcskcI0jCOTnEc06UY4z +OyGr/Sxlj9i7SNfxd58MnI/wPDuZpNuNRACkDkR4jgYANZHoBD0F35rTT1SZa6sM9Hc vFSEAHtWXVoJjRpDP8PcRS0AjJVmWDsk2llaM= 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:content-transfer-encoding; b=wka5+JnutAbaHYipQ2Q55JZNFMZjTMfVPTtRDokYHuY8cU6Dv0AFuZ7qKuWG86KqsQ AfXWtpW0OdeUxn2NnZnik5JAqru2jhjUhEacXiCde65CYGOX0Tw8z4kA3iHk82+8GMIQ W+sG6ZkoQhAeU4e1JuQ1C0TdrO8SSNwxMGKKI= MIME-Version: 1.0 Received: by 10.204.122.74 with HTTP; Wed, 14 Apr 2010 12:02:00 -0700 (PDT) In-Reply-To: References: <20100414174853.GC43908@dan.emsphone.com> Date: Wed, 14 Apr 2010 15:02:00 -0400 Received: by 10.204.142.207 with SMTP id r15mr301269bku.134.1271271720648; Wed, 14 Apr 2010 12:02:00 -0700 (PDT) Message-ID: From: Leinier Cruz Salfran To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 19:02:02 -0000 On Wed, Apr 14, 2010 at 2:50 PM, Freddie Cash wrote: > 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. =C2=A0When library= ports > go through a library bump like this, all the ports that depend on it get = an > automatic PORTREVISION bump. > okey maybe i didn't understood the 'bump' means .. I must to thank you because of comment about this subject > All the port maintainer has to do is double-check that the port compiles > with the new version of the lib. =C2=A0Only if there are issues with that= (which > usually get picked up by the -exp runs on the ports cluster), then the po= rt > maintainer has to step in and fix things. > okey let me see if I understood you .. you mean that I create a 'ONE_PORT' to a specific program version and if one of the library on which the 'ONE_PORT' depends change to a major version, then the 'ports cluster' put add PORTREVISION to the 'ONE_PORT' and update the *_DEPENDS automatically???????? > 9 times out of 10, a port maintainer doesn't have to do anything with a p= ort > until a new version of the app is released. > okey okey do not repeat again .. I read 9 times out of 10 ;) > >> 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 anythi= ng > like this. =C2=A0A 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 a= nd > 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. > =C2=A0Overall, not a long process. > > If you maintain enough ports for enough time, and generate enough committ= ed > PRs to annoy people enough, you get rewarded with a commit bit. =C2=A0:) > oohh .. thanks for the tip :)