Re: portupgrade -P and local changes

2004-12-27 Thread Harlan Stenn
I looked at pkgtools.conf, and I don't see a way to do what I want there. My goal here is to make it *easy* for somebody to update the installed ports on a machine. Even if we could use MAKE_ARGS in pkgtools.conf to try and do this that does not solve the problem I am seeing. (There is a bigger

Re: portupgrade -P and local changes

2004-12-26 Thread Chris
Kris Kennaway wrote: On Sun, Dec 26, 2004 at 09:41:04PM -0600, Chris wrote: Neither -x nor HOLD_PKGS is what I want. Er..the thread started with a question from a user who *knows about -P and uses it*, but doesn't want portupgrade to fetch packages in a specific situation. Kris Again, from the m

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 07:38:10PM -0800, Harlan Stenn wrote: > I think a fair number of people would like to see it. > > It would make it Lots Easier for people to upgrade their systems. > > There are packages where it makes lots of sense to use the prebuilt ones. > > Now that I think the only

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 09:41:04PM -0600, Chris wrote: > >Neither -x nor HOLD_PKGS is what I want. > >>Er..the thread started with a question from a user who *knows about -P > >>and uses it*, but doesn't want portupgrade to fetch packages in a > >>specific situation. > >> > >>Kris > > > > > >

Re: portupgrade -P and local changes

2004-12-26 Thread Chris
Chris wrote: Kris Kennaway wrote: On Sun, Dec 26, 2004 at 09:22:04PM -0600, Chris wrote: Kris Kennaway wrote: On Sun, Dec 26, 2004 at 06:53:09PM -0800, Harlan Stenn wrote: Neither -x nor HOLD_PKGS is what I want. I *want* to upgrade the software, I just do not want to FETCH prebuilt packages for a

Re: portupgrade -P and local changes

2004-12-26 Thread Harlan Stenn
I think a fair number of people would like to see it. It would make it Lots Easier for people to upgrade their systems. There are packages where it makes lots of sense to use the prebuilt ones. Now that I think the only feature I want is for it to "don't fetch if there is a Makefile.local" I'll

Re: portupgrade -P and local changes

2004-12-26 Thread Chris
Kris Kennaway wrote: On Sun, Dec 26, 2004 at 09:22:04PM -0600, Chris wrote: Kris Kennaway wrote: On Sun, Dec 26, 2004 at 06:53:09PM -0800, Harlan Stenn wrote: Neither -x nor HOLD_PKGS is what I want. I *want* to upgrade the software, I just do not want to FETCH prebuilt packages for any package th

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 09:22:04PM -0600, Chris wrote: > Kris Kennaway wrote: > >On Sun, Dec 26, 2004 at 06:53:09PM -0800, Harlan Stenn wrote: > > > >>Neither -x nor HOLD_PKGS is what I want. > >> > >>I *want* to upgrade the software, I just do not want to FETCH prebuilt > >>packages for any packag

Re: portupgrade -P and local changes

2004-12-26 Thread Chris
Kris Kennaway wrote: On Sun, Dec 26, 2004 at 06:53:09PM -0800, Harlan Stenn wrote: Neither -x nor HOLD_PKGS is what I want. I *want* to upgrade the software, I just do not want to FETCH prebuilt packages for any package that has a Makefile.local file in the tree, as a Makefile.local file means I wa

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 06:53:09PM -0800, Harlan Stenn wrote: > Neither -x nor HOLD_PKGS is what I want. > > I *want* to upgrade the software, I just do not want to FETCH prebuilt > packages for any package that has a Makefile.local file in the tree, as > a Makefile.local file means I want to buil

Re: portupgrade -P and local changes

2004-12-26 Thread Harlan Stenn
Neither -x nor HOLD_PKGS is what I want. I *want* to upgrade the software, I just do not want to FETCH prebuilt packages for any package that has a Makefile.local file in the tree, as a Makefile.local file means I want to build that package with local changes. H -- On Sun, Dec 26, 2004 at 01:36:1

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 01:36:12PM -0800, Harlan Stenn wrote: > Yes, but that means I have to remember to build and package the ports > first, before I do anything else, and that implies I have to handle any > changed prerequisite packages as well. I thought that's what you were asking for. > If

Re: portupgrade -P and local changes

2004-12-26 Thread Harlan Stenn
Yes, but that means I have to remember to build and package the ports first, before I do anything else, and that implies I have to handle any changed prerequisite packages as well. If a way can be found to say "Do not fetch these packages" then this will become a much easier process. H -- >> Is t

Re: portupgrade -P and local changes

2004-12-26 Thread Donald J. O'Neill
On Sunday 26 December 2004 03:04 am, Harlan Stenn wrote: > I have a couple of ports where I am using a Makefile.local to > provide some customizations for the local environment (I think > they are for postfix+SASL, and apache2+the experimental modules, > but I could be mistaken) where "stock" prebu

Re: portupgrade -P and local changes

2004-12-26 Thread Kris Kennaway
On Sun, Dec 26, 2004 at 01:04:51AM -0800, Harlan Stenn wrote: > Is there a way to tell portupgrade that it should not *fetch* prebuilt ports > for these two packages? If the packages are already there I'm fine having > them installed (as it means they were built using the Makefile.local values >

Re: portupgrade -P and local changes

2004-12-26 Thread RW
On Sunday 26 December 2004 09:04, Harlan Stenn wrote: > I have a couple of ports where I am using a Makefile.local to provide some > customizations for the local environment (I think they are for > postfix+SASL, and apache2+the experimental modules, but I could be > mistaken) where "stock" prebuilt