Date: Sun, 13 Aug 2006 13:24:42 -0400 From: Randy Pratt <bsd-unix@earthlink.net> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: Kiffin Gish <kiffin.gish@planet.nl>, freebsd-ports@freebsd.org, Rene Ladan <r.c.ladan@gmail.com> Subject: Re: Skipping certain ports, no upgrade of installed packages ... Message-ID: <20060813132442.e3550e78.bsd-unix@earthlink.net> In-Reply-To: <44DF389F.9010807@gmx.de> References: <1155466969.52536.15.camel@localhost> <44DF0843.8010303@gmx.de> <1155467479.52536.20.camel@localhost> <44DF0DFF.9000105@gmail.com> <20060813091219.a2d5377e.bsd-unix@earthlink.net> <44DF389F.9010807@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Aug 2006 16:35:11 +0200
"[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> wrote:
>
> Randy Pratt wrote:
> > On Sun, 13 Aug 2006 13:33:19 +0200
> > Rene Ladan <r.c.ladan@gmail.com> wrote:
> >
> >> Kiffin Gish schreef:
> >>> On Sun, 2006-08-13 at 13:08 +0200, [LoN]Kamikaze wrote:
> >>>> Kiffin Gish wrote:
> >>>>> How can prevent a given package from being reinstalled during the next
> >>>>> portupgrade when I want to delete permanently?
> >>>>>
> >>>>> An example is the Galeon browser. Since it also appears in the
> >>>>> gnome2-fifth-toe makefile t will automatically be rebuilt.
> >>>>>
> >>>>> 2nd question: how can I just keep a given version without having it
> >>>>> upgraded?
> >>>>>
> >>>>> Thanks alot in advance.
> >>>>>
> >>>> .if ${.CURDIR:M/usr/ports/category/port}
> >>>> IGNORE= not wanted
> >>>> .endif
> >>>>
> >>>> This will keep the ports system from building them. But you will have to
> >>>> edit dependant ports Makefiles. I'm doing that for arts and have to edit
> >>>> the kdelibs Makefile every time kdelibs gets updated.
> >>> The only problem with that approach is that every time I run cvsup the
> >>> modified makefiles are overwritten.
> >>>
> >>> Can also just delete the dependencies line containing galeon for
> >>> example, but overwritten by next cvsup.
> >>>
> >> You can also try portsnap, which only overwrites ports which have been
> >> changed by a commit.
> >
> > I'm not sure that is true for portsnap under all conditions. From
> > the portsnap man page:
> >
> > extract Extract a ports tree, replacing existing files and
> > directories. NOTE: This will remove anything occupying
> > the location where files or directories are being
> > extracted; in particular, any changes made locally to
> > ports tree (for example, adding new patches) will be
> > silently obliterated.
> >
>
> You forget that extract is only called for the first time portsnap is used.
> Afterwards you use 'portsnap fetch update', which has the desired behaviour.
Actually, I didn't forget. I was pointing out that portsnap will
remove any local patches/modifications in an existing ports tree when
extract is used. I think we both agree on this.
Randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060813132442.e3550e78.bsd-unix>