On 14 Jul 2013, at 08:29, Teske, Devin wrote: > > To give you an idea as to just how helpful this is... > > Imagine the following hierarchy: > > src/pkgbase/depend/mystuff/script1 > src/pkgbase/depend/mystuff/textfile1 > src/pkgbase/depend/mystuff/sourcefile.c > src/pkgbase/depend/mystuff/Makefile > > You are a developer. You want to ship a package that contains "script1", > "textfile1", and "binary1" (which is compiled by saying "make" to turn > "sourcefile.c" into "binary1") > > You want to ship 8 types of packages: > > FreeBSD-4.11 > FreeBSD-8.1 (i386) > FreeBSD-8.1 (amd64) > RedHat EL 4 > RedHat EL 6 (i386) > RedHat EL 6 (x86_64) > Debian Wheezy > Debian Wheezy 64-bit > > This is where my framework comes in-handy... > > cd ~/src/pkgbase/freebsd/RELENG_4/category/mystuff > make > # it pulled the necessary bits from "src/pkgbase/depend/mystuff" and built > the .tgz > > cd ~/src/pkgbase/freebsd/RELENG_8/category/mystuff > make > # it pulled the necessary bits from the "depend" dir and built .tbz > > cd ~/src/pkgbase/redhat/rhel4/category/sub-category/mystuff > make > # pulled in "depend" and made .rpm > > cd ~/src/pkgbase/redhat/rhel6/category/sub-category/mystuff > make > # pulled in "depend" and made .rpm > > etc. > > Of course, *any* time the depend tree has binaries in it... you have to first > do a make in there on the platform you want to ship the binary for, and then > do "make depend" in the platform-specific tree to pull in the binaries. Once > you've done that, you don't have to muck with the depend tree again unless > there are changes there. > > So, I assume that your prejudice remarks are because you haven't either seen > (a) such a platform or (b) such a need for said platform. > > Yeah, I could rewrite the freebsd-specific logic to use "pkg create", but let > me tell you... > > When you have to touch a file that needs to get shipped out to multiple > platforms... > > It's damned nice to be able to build the FreeBSD packages under RedHat > *BECAUSE* the redhat RPMs can't be built under anything else (building an RPM > on FreeBSD and attempting to install it on RedHat results in an error message > similar to "this is an rpm for FreeBSD; go away"). > > Whereas FreeBSD will never balk about a package built on another platform. > > It's a huge time-saving measure... not having to jump over to each/every > unique platform to package things up *IF/WHEN* you know that there are no > binaries in the package *or* you've already checked the pre-compiled binaries > into the arch-specific hierarchy. > > > > >> Or you >> can maintain the old cruft for your business -- just don't expect >> anyone else to use it, or even want to. >> > > > I have no intention of making old-world packages... but I also have no > intention of using "pkg create".
You still haven't really explained at all why you can't use libpkg. If it doesn't run on Debian (not tried), it's got to be easier to port it than rewrite a hacked version, hasn't it??? At least then you'll also be contributing back. Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
