Re: ports on a CD

From: Kris Kennaway (kris_at_obsecurity.org)
Date: 09/23/03

  • Next message: David Smith: "Mouse issues"
    Date: Tue, 23 Sep 2003 09:25:02 -0700
    To: Tadimeti Keshav <keshav_tadimeti@yahoo.co.uk>
    
    
    

    On Tue, Sep 23, 2003 at 05:04:59PM +0100, Tadimeti Keshav wrote:

    > > What are you really asking here? First you ask for
    > > ports (but the
    > > ports collection is on CD1), then you say debian
    > > includes packages on
    > > their CDs (so does FreeBSD).
    > >
    > Well, remember that the ports collection is nothing
    > but the skeleton that can connect to the internet and
    > fetch the source files that you can compile. What I
    > was asking for is the facility to have all the sources
    > of all the ports on the CD. (SO you needn't connect to
    > the internet to build your machine).

    The full set of distfiles takes up 15GB, i.e. about 21 CDs. Is that
    really practical? ;-)

    See however the FreeBSD PowerPak sold by FreeBSDMall.com.

    > > > I think the FreeBSD distribution would be better
    > > off
    > > > having all ports on the 2 additional CDs rather
    > > than
    > > > have packages.
    > >
    > > Now you say "ports rather than packages", when both
    > > are shipped.
    > >
    > > Can you please clarify what you are asking?
    > >
    > > Kris
    > Debian ships all DEB packages on the CDs.

    I doubt it.

    > FreeBSD only
    > bundles some packages. For example, JDK is a port
    > while vim is a package.

    JDK may not be packaged due to the restrictive license on the
    software. The same is true for most of the other ports that are not
    packaged (other reasons include that the port is broken or forbidden
    because it contains a security vulnerability).

    Also, a full package set is about 5GB (for i386), which would take
    about 7 CDs. Again, not really practical.

    > Would it not be better to cut
    > down on several packages of large size and ship the CD
    > with the sources needed to compile JDK etc.

    No, because we would be sued by Sun.

    Kris

    
    



  • Next message: David Smith: "Mouse issues"

    Relevant Pages

    • Re: portupgrade O(n^m)?
      ... wanted to try and port sections of portupgrade and its related tools to ... in 15 mn to 20 mn you have your packages. ... because packages don't break when compiling. ... pkg_add for around 500 ports replaced. ...
      (freebsd-hackers)
    • Re: portupgrade O(n^m)?
      ... in 15 mn to 20 mn you have your packages. ... >> because packages don't break when compiling. ... >> packages for installation are already present on the machine. ... >> modifying the origins of the ports. ...
      (freebsd-hackers)
    • Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
      ... It is better to use all ports or all packages so either do: ... people install php at all. ... And yes there are some ports that don't have packages for licencing ... Preferring cvsup to portsnap is kinda like preferring vim ...
      (freebsd-questions)
    • Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db
      ... The only problems I've ever seen with installing packages is that at ... And yes there are some ports that don't have packages for licencing etc ... though I can't recall ever having to install one of those. ... >> Preferring cvsup to portsnap is kinda like preferring vim over ...
      (freebsd-questions)
    • Re: newbie package/ports questions
      ... I have an updated ports tree using portsnap (fetched and extracted ... everything compile from ports and it seems to work fine, but packages ... would of course be faster to install. ... portupgrade -NPRr kde ...
      (comp.unix.bsd.freebsd.misc)