Date: Thu, 8 Feb 2001 21:32:37 -0800 From: Jeremy Lea <reg@FreeBSD.ORG> To: "Bruce A. Mah" <bmah@FreeBSD.ORG> Cc: freebsd-ports@FreeBSD.ORG Subject: Re: [RFC] make upgrade target for bsd.port.mk Message-ID: <20010208213237.K8780@shale.csir.co.za> In-Reply-To: <200102090240.f192e9u13590@bmah-freebsd-0.cisco.com>; from bmah@FreeBSD.ORG on Thu, Feb 08, 2001 at 06:40:09PM -0800 References: <200102082347.f18NlgO12046@bmah-freebsd-0.cisco.com> <20010208182123.I8780@shale.csir.co.za> <200102090240.f192e9u13590@bmah-freebsd-0.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Thu, Feb 08, 2001 at 06:40:09PM -0800, Bruce A. Mah wrote: > I disagree (with your first sentence). You can only do pkg_add if you > have a package constructed. The only way to make a package (currently) > from a port is to actually install all the files. http://people.freebsd.org/~reg/ > Hmmm, I wonder does this need to be generalized to include other kinds > of files too? I had thought of just merging in the old +CONTENTS file with the new +CONTENTS and leaving all of the old files behind, but that would be a mess for things which often do big changes in directory structure (like GNOME, KDE or Mozilla). At the moment I think we can follow the route of making things work in the default case, and then working on fixing the corner cases as people find them. Mostly, if you just upgrade a package at the base of a whole tree (like GTK+ or ghostscript often are) then, if things break in the packages which required these, generally you can also upgrade this package to the latest package via Ports/Packages, and things will work. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010208213237.K8780>