Welcome to FreeBSDFreaks.net!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Clarification on fetch/extract targets

 
   FreeBSD Hosting (Home) -> FreeBSD Ports RSS
Next:  Upgrading to amd64 requires recompilation of port..  
Author Message
Stephen Hurd

External


Since: Jan 30, 2004
Posts: 4



(Msg. 1) Posted: Sat Jun 16, 2007 6:16 pm
Post subject: Clarification on fetch/extract targets
Archived from groups: mailing>freebsd>ports (more info?)

So, I created a new port (ports/113608) for Code::Blocks which has not
had a source code release for almost two years despite constant
development. However, the currently correct way to get the source is
via subversion. The port currently does this, but I'm unsure of exactly
what is required by the fetch and extract targets, so I'm not sure what
the "right" thing to do here is. I can think of a few possibilities:

1) The fetch target is intended to do all the steps which require a
network connection and extract is intended to places the files into WRKSRC
- In this case, the fetch target would use svn co to WRKSRC and the
extract target would do nothing. This is what the port currently does.

2) The fetch target is intended to place source archives into DISTDIR
and extract is intended to place them into WRKSRC
- In this case, the extract target would use svn co to WRKSRC and the
fetch target would do nothing.

3) The fetch target is intended to place a source archive in DISTDIR and
the extract target is intended to extract that archive into WRKSRC
- Here I would need to do the svn checkout in the fetch target, archive
it, then delete it.

4) The fetch target retrieves sources in the distribution format and
extract places them into WRKSRC
- In this case, you would svn co to a DIST_SUBDIR in fetch, then extract
would copy that to WRKSRC

5) fetch *MUST* fetch a source archive into DISTDIR. None of this
svn/CVS checkout stuff in the ports tree.
- Hrmph. So rather than bumping PORTREVISION to the desired subversion
revision and having it Just Work, one needs to make a source archive and
host it somewhere himself and be responsible for updating it himself too.
_______________________________________________
freebsd-ports RemoveThis @freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"

 >> Stay informed about: Clarification on fetch/extract targets 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
can't extract zip - Hi, why will this not extract correctly ? (this is just the beginning of nant) I get the following error and I can't figure out what the heck I'm doing wrong. $ make extract < --- SNIP --- > ===> Extracting for nant-0.84 >> Checksum ...

extract once and build many? - Hi all I noticed that some ports, e.g. qt-4 stuff, just use the same source ball but extract it each time for their own build. Is there some method to reuse the extracted sources? I think it is perhaps a waste of cpu and time to extract the....

extract both bz2 and gz files from distfiles - Hi! We have got a port (lang/gnat-gcc34) which has both bz2 and gz distfiles. As for 5.x+ extracting is gone automagically. But not at 4.x. Well, at 4.x extracting may be done for example, by using USE_BZIP2 knob and doing gunzipping at after-extract:....

astro/luna mysterious extract/patch problem - Running either of these commands in /usr/ports find . -type d -mindepth 2 -maxdepth 2 ! -name CVS | grep -vE '^\./[[:upper:]].*' | while read d; do (cd $d; echo "&&&&&& $d &&&&&&"; rm -r...

Need sparc64 help with a port build error: unable to extract - Howdy, I have the following unbuildable port error on sparc64 for fpdns: ====================<phase 4: make build>==================== add_pkg perl-5.8.7.tbz adding dependencies pkg_add perl-5.8.7.tbz man/man1/perlvar.1.gz: (Empty error message)....
   FreeBSD Hosting (Home) -> FreeBSD Ports All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]