summaryrefslogtreecommitdiffstats
path: root/Mk
Commit message (Collapse)AuthorAgeFilesLines
* Adjust comments to document MASTER_SITES and remove mention ofjkh1994-09-131-5/+2
| | | | HOME_LOCATION.
* Ok, I think I have this whole HOME_LOCATION / MASTER_SITE stuff resolvedjkh1994-09-131-10/+14
| | | | | | | | | | | | | | | | | to a reasonable compromise: MASTER_SITES now contains a space seperated list of sites for which each DISTFILE may be retrieved. This should be a directory spec, which will be concatenated with each file in DISTFILES. HOME_LOCATION is *gone* now and isn't used for anything, so you can delete it from your Makefiles. If you want to force a fetch from a given location, simply do something like: MASTER_SITES= ftp://fnord.foo.bar/pub/dist DISTFILES= a.tar.gz b.tar.gz Your entry in MASTER_SITES will be tried first to fetch a.tar.gz and b.tar.gz, followed by any master sites we have set up (right now, only freebsd.cdrom.com).
* More fixes and general cleanup. Add more fine-grained control over whatjkh1994-09-111-15/+25
| | | | is fetched and what is actually unpacked.
* Whoops, forgot to stop this lurking typo, too.jkh1994-09-111-2/+1
|
* Eliminate a few lurking bogons - this is almost close to being right!jkh1994-09-111-4/+13
|
* Annual simplification drive:jkh1994-09-101-110/+95
| | | | | | | | | | | | | | | 1. DISTFILE is gone and replaced by DISTFILES, which can contain one or more file specifications. 2. MASTER_SITE created, which points to the distfiles directory on freebsd.cdrom.com (which I'll set up in a moment). 3. HOME_LOCATION is now simply a hint, and is never directly used except to inform the user when ncftp unable to transfer a file from MASTER_SITE. 4. ncftp is now assumed to live somewhere in the path, in preparation for Andrew bringing it in on a more permanant basis. 5. XMKMF defined - it was not before. Thanks to Andrew (ache) for many helpful suggestions.
* Rearrange this a bit while I think about the whole problem of fetchingjkh1994-09-091-50/+55
| | | | | | | | | | | multiple targets when dealing with creating a set of distribution files from scratch. Another problem is *verifying* that a given file fetched from its HOME_LOCATION is the one we wanted (what if the stupid ftp site maintainer updated it in place?). Rich Morin pointed this out and suggested some solutions. I need to think about it some more (suggestions?). For now, we have a seperate `fetch' and `extract' target. Submitted by: jkh
* As per suggestion by Michael Reifenberger, make ncftp use the -N flag.jkh1994-09-091-2/+3
| | | | | Reviewed by: jkh Submitted by: mr
* Fixed a couple of typos. Ok, this works now. Only one significant hurdlejkh1994-09-021-5/+5
| | | | | | | | | | remains, and that's that this does not work with multiple targets, which sort of throws the tk and fvwm distributions into a mess. tk needs both a tarball and a patch file from the same site, fvwm needs up to 3 different files if you want all the options. If anyone wants to take this the last few steps of the way towards somehow handling cases like this, I'd be very happy. Submitted by: jkh
* Ok, I've reviewed this and made it work now. ncftp fetching seems to bejkh1994-09-021-17/+16
| | | | | working/closer to working now. Submitted by: jkh
* Add a few missing >> lines to error echo's.. This is basically myjkh1994-09-021-4/+4
| | | | | convention to make searching for error messages easy. Submitted by: jkh
* Here's my first cut at doing auto-fetch with ncftp. The extract rulejkh1994-09-011-7/+31
| | | | | is turning into the original make rule from hell! Submitted by: jkh
* Geeze, what was I thinking again? Replace all references to:jkh1994-09-011-7/+15
| | | | | | | | | | | | | | | | | | | | | ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX} With simply `${DISTFILE}' which defaults to the above. This lets you easily name distribution files that don't cooperate with any rational naming syntax. Similarly, make a variable called ${PKGFILE} which fills the same purpose for packages. Just trying to make this thing really really general to suit every need. Now I need somebody to figure out how to make the extract target auto-fetch things from ${HOME_LOCATION} with ncftp *if* ncftp is installed and it looks possible to reach the foreign site. That will take some fancy footwork, but would be slick. I've changed this too so that HOME_LOCATION is no longer set by default, allowing you to do an .if defined(..) check for it. The extract rule now does this too. Submitted by: jkh
* added hook for post-build scriptadam1994-08-301-1/+4
| | | | | Reviewed by: Submitted by:
* Lots of changes - get the NO_XXX things over, add @'s to the touches forjkh1994-08-281-20/+74
| | | | | | default extract and configure targets, add a pre-clean since I need it for pkg_install port. Submitted by: jkh
* Add a pre-configure rule after all, since it's helpful to be ablejkh1994-08-251-6/+7
| | | | | | to also run a rule before you apply patches and then go into the 3 stage script configuration. This bit Adam David in his dgd port. Submitted by: jkh
* Also `make Makefiles' in USE_IMAKE case to catch subdirs.jkh1994-08-251-2/+2
| | | | Submitted by: jkh
* Sigh. I am a hosebrain. I've been using gmake for so long, I'vejkh1994-08-251-21/+6
| | | | | started using some of its features reflexively. Submitted by: jkh
* Add a new flag: USE_IMAKEjkh1994-08-251-1/+4
| | | | | This will cause the configure pass to do an `xmkmf' if set. Submitted by: jkh
* Some cosmetic changes.jkh1994-08-241-7/+56
| | | | | | | | | Add pre-{build,extract,install,...} targets for Torsten, who apparently needs them. Can't do effective post-* targets without major work, sorry. Jordan Reviewed by: Submitted by:
* Ok, this should work with a centralized package directory now (so youjkh1994-08-221-6/+5
| | | | | can elect to dump all finished packages in one directory). Submitted by: jkh
* Make package target a lot more general.jkh1994-08-221-6/+14
| | | | Submitted by: jkh
* Whoops - left out the package rule!jkh1994-08-221-1/+5
| | | | Submitted by: jkh
* Use proper proper package suffix.jkh1994-08-221-2/+2
| | | | Submitted by: jkh
* Whoops, left out a backslash in my package rule.jkh1994-08-221-4/+4
| | | | Submitted by: jkh
* Ok, now we warn if we're about to recreate the distfile from configuredjkh1994-08-221-7/+12
| | | | | | sources. Configuring doesn't always _do_ anything, which is why it's a warning and not an error. Submitted by: jkh
* New bsd.port.subdir.mk file for use by ports. This groks all thejkh1994-08-222-42/+60
| | | | | | | | | | | | | | | | | | | special ports building targets and will recurse properly. Sorry, Julian E - no fancy prompts, just recursion! :-) Added a `bundle' target. Purpose is as follows: You want to give someone a complete tree sans distfiles (for sticking on CDROM perhaps?) but the difficulty there is that the first time the user types `make clean', all the unpacked sources are gone again. Typing `make bundle' recreates the original distfile if it can, so someone can "back up" their unpacked tree easily with one command. Whoops, just thought of something - it should warn if you configured the working source. Ok, next commit! :) Submitted by: jkh
* I had to bite the bullet: There's now a port.subdir.mk that does the rightjkh1994-08-222-3/+91
| | | | | | thing with recursive build, configure, bundle or extract targets. Reviewed by: Submitted by:
* Sigh.. Some of these configs are a little hairy. I need to know thejkh1994-08-211-5/+5
| | | | | ${PORTSDIR} too now - pass it to any and all config scripts. Submitted by: jkh
* Make things a little more user-friendlyjkh1994-08-211-3/+5
| | | | Submitted by: jkh
* Get the .configure_done stuff working - it wasn't in the right place.jkh1994-08-211-3/+3
| | | | Submitted by: jkh
* Start really adding some features here. Let's see:jkh1994-08-211-8/+33
| | | | | | | | | | | | | | | | 1. New variable DEPENDS lets you list packages that this depends on, relative to the top (lang/tcl, x11/tk, etc). These packages will always get made first. 2. Don't configure again if you've already done so successfully. 3. Add pre-configure and post-configure hooks. You can now do a pre-configure, a local configure, a port-provided configure and finally a post-configure if you really really want to. I can't imagine anything this will leave us not being able to do! :) [ Yes, I have actually found a use for at least two of these in one port - see x11/tk!]. Submitted by: jkh
* Simplify the whole configuration script business quite a bit. Whatjkh1994-08-211-9/+5
| | | | | was I thinking before.. Submitted by: jkh
* Whoops, the check for a missing distfile was slightly bogus. Now it works.jkh1994-08-211-10/+11
| | | | Submitted by: jkh
* Make any local configuration file unconditional. That is, if one existsjkh1994-08-211-8/+8
| | | | | then run it even if GNU configure is to be run later. Submitted by: jkh
* Commit my new ports make macros. Still not 100% complete yet by any meansjkh1994-08-211-0/+152
but fairly usable at this stage. Submitted by: jkh
OpenPOWER on IntegriCloud