Re: cvsup with tag=. on src and upgrading (in general)

From: peter lageotakes (plageotakes_at_yahoo.com)
Date: 06/14/03

  • Next message: Brandon S. Allbery : "Re: cvsup with tag=. on src and upgrading (in general)" 
    Date: Fri, 13 Jun 2003 20:15:57 -0700 (PDT)
To: Richard Schilling <rschi@rsmba.biz>, freebsd-stable@freebsd.org

    Thanks Richard,

    I kind of start to rethink about my original choice of
    tags based on:

    <quote>
    Section A.6 contains branch tags that users might be
    interested in.
    When specifying a tag in CVSup's configuration file,
    it must be
    preceded with tag= (RELENG_4 will become
    tag=RELENG_4). Keep in mind
    that only the tag=. is relevant for the ports
    collection.
    </quote>

    But the quote below is says:
    Note: The ports tree does not have any tag associated
    with it, it is always CURRENT.

    I guess it means that it will just delete and install
    the ports collection no matter what the tag points
    too.

    I had to do a sanity check. I started second guessing
    myself.

    Pete

    --- Richard Schilling <rschi@rsmba.biz> wrote:
    > Thanks for all the help folks. The documentation
    > does come up a bit
    > shy on clarity (no offense) - found myself guessing
    > a bit . . .
    >
    > I know that tag=. specifies the HEAD node, but I was
    > a bit confused by
    > the documentation. It does say that
    > *default tag=.
    >
    > will retreive FreeBSD-CURRENT, and when tag and date
    > are absent you get
    > the RCS files. My bad I guess.
    >
    > But, the documentation confused me with this:
    >
    > <quote>
    >
    > For our example, we wish to receive FreeBSD-CURRENT.
    > We add this line
    > at the beginning of our supfile:
    >
    > *default tag=.
    >
    > There is an important special case that comes into
    > play if you specify
    > neither a tag= field nor a date= field. In that
    > case, you receive the
    > actual RCS files directly from the server's CVS
    > repository,
    >
    > </quote>
    >
    > followed by this . . .
    >
    > <quote>
    > Section A.6 contains branch tags that users might be
    > interested in.
    > When specifying a tag in CVSup's configuration file,
    > it must be
    > preceded with tag= (RELENG_4 will become
    > tag=RELENG_4). Keep in mind
    > that only the tag=. is relevant for the ports
    > collection.
    > </quote>
    >
    > So, I am not sure what tag=. fetches when run on
    > src-all. It it
    > invalid (unpredictable) or actually FreeBSD-CURRENT?
    >
    > I don't have the example cvsup files in
    > /usr/share/examples/cvsup. Did
    > I not install a port?
    >
    > --Richard Schilling
    > _______________________________________________
    > freebsd-stable@freebsd.org mailing list
    >
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    > To unsubscribe, send any mail to
    "freebsd-stable-unsubscribe@freebsd.org"

    __________________________________
    Do you Yahoo!?
    SBC Yahoo! DSL - Now only $29.95 per month!
    http://sbc.yahoo.com
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Brandon S. Allbery : "Re: cvsup with tag=. on src and upgrading (in general)"

    Relevant Pages

    • Re: release in cvsup supfile
      ... Should I change the tag to 5.4-RELEASE? ... and the other for ports and everything else so keep reading.... ... Tracks -CURRENT, currently FreeBSD 7, it's for developers. ... Now install FreeBSD, delete the old slices first with fdisk and don't ...
      (freebsd-questions)
    • Re: cvsup tag for ports
      ... As I've studied the FreeBSD Handbook as well as the man pages for this, it's still not clear to me which tag I should use for a production server. ... For my sources I always use the security branch for the release we are using so that they stay stable and also plug most of the security issues as they arise and so the sources tag is always RELENG_6_2. ... On one hand it makes sense to track that branch for ports because that's where fixes would go for applications as they find them, but I'm not convinced this is the best thing for a production server and wonder if I should also use the security branch for the ports. ... Neither the ports tree nor the docs tree is branched. ...
      (freebsd-questions)
    • Re: cvsup tag for ports
      ... it's still not clear to me which tag I should use for a production server. ... For my sources I always use the security branch for the release we are ... On one hand it makes sense to track that branch for ports because that's ... Neither the ports tree nor the docs tree is branched. ...
      (freebsd-questions)
    • Re: which ports tag should i follow?
      ... cvsup src-all, and now i don't know which ports tag to cvsup? ... does ports cvs tree have RELENG_7 tag too, or i should follow tag "."? ... sudo portsnap fetch extract ...
      (freebsd-questions)
    • Re: VAX-11/782 -- memory system?
      ... The MA780s had multiple ports, and a set of tag bits for each memory ... On a read from a port, that tag bit was set. ... care about the invalidation so did not have to be interupted. ... The notion that including non-shared MS780 memory would have screwed SMP ...
      (comp.sys.dec)