Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Dec 2015 22:05:11 -0800
From:      Waitman Gobble <gobble.wa@gmail.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: Migrating to FreeBSD from Debian
Message-ID:  <CAFuo_fza1p15LW54naKQTpkqeqNqsWR=eagr6-PcAuYhtBaL9g@mail.gmail.com>
In-Reply-To: <20151208062508.31ae2ec2.freebsd@edvax.de>
References:  <CAO-kBwffucnPVphm_ajbtAejjFiAv_Cp+v7jZ-xCTX7YTqk36w@mail.gmail.com> <86poyiuynx.fsf@gmail.com> <CAA2O=b_p-HPx+pPyFOgJMe02d5xrJe_aXJ8ZG9z+dHZCNwh91Q@mail.gmail.com> <56659FC8.8020904@FreeBSD.org> <CAA2O=b-dQMpnq=nJ6RMSvwBCa4kP4PB2k4c7nbTVrwtQkzStBg@mail.gmail.com> <20151208062508.31ae2ec2.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, Dec 7, 2015 at 9:25 PM, Polytropon <freebsd@edvax.de> wrote:

> On Mon, 7 Dec 2015 17:10:00 +0200, Anton Sayetsky wrote:
> > 2015-12-07 17:03 GMT+02:00 Matthew Seaman <matthew@freebsd.org>:
> > > ... and a package is what you get by compiling a port.  Yes, there is a
> > > difference, but the two things are often conflated and it isn't worth
> > > muddying the waters by insisting on exactingly precise terminology from
> > > people new to FreeBSD.  It is clear enough what they mean -- their aim
> > > is to get some software installed or upgraded.
> > But we should warn then about not mixing ports & packages. I agree,
> > pkg is a good choice [when pkg only].
>
> That's not a big deal anymore. If you use the default options
> for building a port (like those from which the package would
> be generated), no precautions are needed. If you use different
> options, for only _few_ ports, use "pkg lock" and "pkg unlock".
> If you need to compile many ports and still want to use packages,
> check out "poudriere". Ports and packages can co-exist happily. :-)
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe@freebsd.org"
>



The machines I use mostly run FreeBSD-CURRENT or Debian unstable on a
mainline Linux system. If you are not so interested in matters regarding
license, then the biggest difference you will see is that ports/packages
are installed in /usr/local, while the BSD system is in /usr. It's possible
to delete /usr/local and start fresh, without botching your system.  So we
have a system of user software mostly isolated from operating system.
Sometimes it's easier to start fresh, especially if you have a system which
has not been updated in several months, which can cause seemingly
chicken-and-egg kinds of problems. Most software configurations are in your
home directory, so it's pretty easy to rebuild and not lose any settings.

A Debian system is not configured in such a way, everything is co-mingled,
co-related, co-linked (in /usr). Your /usr/local will be completely empty,
unless you compile something and intentionally install it there.

Additionally, in my opinion, a FreeBSD system is much more 'hackable'. If
you take a look at the source code of the kernel and FreeBSD system, it's
very well documented, easy to change and fiddle with to suit your needs.
and recompile.

There have been times when ports and packages were out of sync, the port
version might be newer than the available package, and this reason is
essentially why it could be problematic to mix ports and packages. In the
past this has caused some issues and inconvenience, however in recent years
it seems packages are typically in sync with ports tree.

-- 
Waitman Gobble
Los Altos California USA
650-900-8557



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAFuo_fza1p15LW54naKQTpkqeqNqsWR=eagr6-PcAuYhtBaL9g>