Date: Sun, 15 Jul 2007 22:44:28 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Tim Kientzle <tim@kientzle.com> Cc: hackers@FreeBSD.org, rwatson@FreeBSD.org, cperciva@FreeBSD.org Subject: Re: Tar output mode for installworld Message-ID: <20070715194427.GB7126@kobe.laptop> In-Reply-To: <46998A66.4030503@kientzle.com> References: <46992FFF.7010906@kientzle.com> <20070715002708.GA3665@kobe.laptop> <46998A66.4030503@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2007-07-14 19:45, Tim Kientzle <tim@kientzle.com> wrote: >On 2007-07-14 13:20, Tim Kientzle <tim@kientzle.com> wrote: >>> <http://www.freebsd.org/projects/ideas/#p-taroutmode>; >>> >>> This is easy to implement using a ... text format such as: >>> bin/sh file /usr/obj/usr/src/bin/sh >>> bin/sh uname root >>> rescue/mkdir hardlink rescue/rescue >>> bin/sh mode 0666 >>> bin/rcp mode 04666 > >Giorgos Keramidas responds: >> A packaging list for one of the distributions I've built at work >> includes stuff like: >> # Misc command-line tools in @prefix@/bin/... >> d none @prefix@/bin 0755 root bin >> f none @prefix@/bin/progname-2.0 0755 root bin >> s none @prefix@/bin/progname=progname-2.0 > > My concern is that "all of the bits for one file" may not always be > available at a single place in the build. Some programs use the > "afterinstall" hook to set flags on the installed binary, for example. Ah, I see now :-) Yes, that would not be easy to support with a single-line format, at least not without some sort of post-processing of the file list. But if we *are* going to need postprocessing, it may as well be a multiline format, like the one you suggested. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070715194427.GB7126>