Skipping certain ports, no upgrade of installed packages ...
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. -- Kiffin Gish [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
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.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
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.
Regards,
Rene
--
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
It won't fit on the line.
-- me, 2001
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
On Sun, 13 Aug 2006 13:33:19 +0200
Rene Ladan [EMAIL PROTECTED] 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.
The conventional tool, portupgrade, uses /usr/local/etc/pkgtools.conf
to HOLD a package (not upgrade). The pkgtools.conf.sample file is
well annotated and has many other available options.
Take a look at that and see if it will do the job.
HTH,
Randy
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
Randy Pratt schreef:
On Sun, 13 Aug 2006 13:33:19 +0200
Rene Ladan [EMAIL PROTECTED] 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.
Running `portsnap extract` will overwrite the ports tree. But `portsnap
update` will only overwrite ports to which a commit has been made.
The conventional tool, portupgrade, uses /usr/local/etc/pkgtools.conf
to HOLD a package (not upgrade). The pkgtools.conf.sample file is
well annotated and has many other available options.
Take a look at that and see if it will do the job.
HOLD_PKGS = ['openoffice*', 'other-port', ]
Note the trailing comma, it is required.
HTH,
Randy
Regards,
Rene
--
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
It won't fit on the line.
-- me, 2001
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
Randy Pratt wrote:
On Sun, 13 Aug 2006 13:33:19 +0200
Rene Ladan [EMAIL PROTECTED] 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.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
On Sun, 13 Aug 2006 16:35:11 +0200
[LoN]Kamikaze [EMAIL PROTECTED] wrote:
Randy Pratt wrote:
On Sun, 13 Aug 2006 13:33:19 +0200
Rene Ladan [EMAIL PROTECTED] 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
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Skipping certain ports, no upgrade of installed packages ...
Kiffin Gish wrote: How can prevent a given package from being reinstalled during the next portupgrade when I want to delete permanently? Unfortunately the real answer here is for these ports to grow OPTIONS. In that way your preferences will be saved in a convenient way that will work with whatever port management tool you choose. The second most convenient way would be to use sysutils/portconf, and add the IGNORE option that LoN suggested. The least convenient way for you to do this and have it persist across port tree upgrades is to write it directly into /etc/make.conf in the manner LoN suggested. 2nd question: how can I just keep a given version without having it upgraded? portupgrade introduced the idea of placing an +IGNOREME file in /var/db/pkg/portname. I recently added support for that feature in portmaster as well. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: maintainer timeout
# [EMAIL PROTECTED] / 2006-05-08 22:27:41 +0200: Hi, I've just discovered that one of my ports has been updated without my approval. The CVS log states maintainer timeout, but I don't recall ever getting a notification. Maybe it got shredded by my spam filter in which case it's entirely my fault of course, but even then I'd still like to see the original PR, which I can't seem to find. So, what went wrong here? http://docs.freebsd.org/cgi/mid.cgi?200602211626.k1LGQjnU044414 Did you ever get a response to this? -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: maintainer timeout
All I see is the following update with the text update to version 9.3.7, approved by: maintainer timeout by danfe (there were no PRs with libticables in the Synopsis): http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/libticables/Makefile?rev=1.16content-type=text/x-cvsweb-markup danfe, any more details here? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
