From owner-freebsd-alpha Sun Feb 24 14:42:36 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id C14E837B421 for ; Sun, 24 Feb 2002 14:42:17 -0800 (PST) Received: from pool0039.cvx22-bradley.dialup.earthlink.net ([209.179.198.39] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16f7LN-0002Di-00; Sun, 24 Feb 2002 14:42:09 -0800 Message-ID: <3C796C34.8D1A42A6@mindspring.com> Date: Sun, 24 Feb 2002 14:41:56 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Riccardo.Veraldi@fi.infn.it Cc: freebsd-alpha@freebsd.org Subject: Re: /usr/ports/security/cfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Riccardo.Veraldi@fi.infn.it wrote: > this port have a lot of unaligned access messages. > What is the standard way to proceed in this case in which the application > is not a distribution program but it is a port collection program? > I imagine contact the port mantainer. > is it correct? Nope. You fix the alignment problems, and then send them to the port maintainer, who probably doesn't own an Alpha machine, and then they include them as the patches. Ideally, as a port, the patches then get sent back to the maintainers of the original code, and they disappear from the port the next time it's updated (_that_ part is done by the maintainer, as well as the initial FreeBSD portability, which doesn't include things like 64 bit cleanliness or the architecture specific changes within an OS, unless the port maintainer has the time and equipment). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message