Date: Tue, 9 Sep 2014 10:43:59 +1000 From: George Michaelson <ggm@pobox.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-pkg@freebsd.org Subject: Re: how do I get apache24 to stay installed with mod_mpm_event and mod_python? Message-ID: <CAM2GGy=zRvXd6FK5TioyvQzOCDaFpysx5TvPqYvcLyNhmwf0qw@mail.gmail.com> In-Reply-To: <540D4BED.5060008@infracaninophile.co.uk> References: <CAM2GGy=wDv26Jd3uuGLiAH=ELabFLy=h2fuDiXCuyebEQo-_RQ@mail.gmail.com> <540D4BED.5060008@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I went with pkg lock for now. its simple. thanks for cluestick. On Mon, Sep 8, 2014 at 4:25 PM, Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > On 08/09/2014 06:41, George Michaelson wrote: >> Whats the canonical recipe to tell pkg and port to "play nice" so you >> can have non-standard builds of things? > > You can hint to pkg(8) to tell it which repository it should install a > package from by using pkg-annotate(8) -- see the 'WORKING WITH MULTIPLE > REPOSITORIES' section pkg-repository(5). > > Beyond that, you can use pkg-lock(8) to force pkg(8) not to overwrite > your customised installs with the defaults from the pkgrepo. Having to > use pkg-lock(8) to override the logic of the dependency solver is not > ideal, but sometimes needs must. > > Right now, installing packages from ports is not treated entirely > equivalently as using a binary package repository. That's an area which > is currently under development: handling various different types of > package sources coherently. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > > PGP: http://www.infracaninophile.co.uk/pgpkey > JID: matthew@infracaninophile.co.uk >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM2GGy=zRvXd6FK5TioyvQzOCDaFpysx5TvPqYvcLyNhmwf0qw>