Re: Call for comments - pkg_trans

2008-07-31 Thread Doug Barton
Norberto Meijome wrote: On Thu, 31 Jul 2008 23:38:21 +0200 "Ivan Voras" <[EMAIL PROTECTED]> wrote: BTW, I thought of another problem scenario. The user installs port M, and it brings dependencies D1, D2, and D3. Then the user installs port N which also has port D2 as a dependency. Port N then w

Re: Call for comments - pkg_trans

2008-07-31 Thread Doug Barton
Ivan Voras wrote: 2008/7/31 Doug Barton <[EMAIL PROTECTED]>: As I'm sure you can imagine, I would not regard any solution that says "portupgrade is mandatory" very favorably, and I don't think I'd be alone there. What you need to be doing here is to define the API so that whatever tool(s) the u

Re: Call for comments - pkg_trans

2008-07-31 Thread Norberto Meijome
On Thu, 31 Jul 2008 23:38:21 +0200 "Ivan Voras" <[EMAIL PROTECTED]> wrote: > > BTW, I thought of another problem scenario. The user installs port M, and it > > brings dependencies D1, D2, and D3. Then the user installs port N which also > > has port D2 as a dependency. > > Port N then won't ins

Unable to make install on Subversion port

2008-07-31 Thread Pierre-Luc Brunet
Hello everybody, I've been trying to install subversion for a few days but it just won't work. I can do make config, make all but when I do make install, it eventually freeze at: chmod 755 /usr/local/libexec/apache22/mod_dav_svn.so I let it like that for an entire day and it never moved

Re: Call for comments - pkg_trans

2008-07-31 Thread Chad Perrin
On Thu, Jul 31, 2008 at 06:25:27AM +0200, Ivan Voras wrote: > Hi, > > I apologize in advance if what I'm trying to do seems stupid or it has > already existed since the Dawn of Time (i.e. when McKusick was in > diapers) but I'd like your comments on this idea: > > http://wiki.freebsd.org/IvanVo

Re: Call for comments - pkg_trans

2008-07-31 Thread Ivan Voras
2008/7/31 Doug Barton <[EMAIL PROTECTED]>: > As I'm sure you can imagine, I would not regard any solution that says > "portupgrade is mandatory" very favorably, and I don't think I'd be alone > there. What you need to be doing here is to define the API so that whatever > tool(s) the user chooses c

Re: Call for comments - pkg_trans

2008-07-31 Thread Marcin Wisnicki
On Thu, 31 Jul 2008 06:25:27 +0200, Ivan Voras wrote: > Hi, > > I apologize in advance if what I'm trying to do seems stupid or it has > already existed since the Dawn of Time (i.e. when McKusick was in > diapers) but I'd like your comments on this idea: > > http://wiki.freebsd.org/IvanVoras/Pkg

Re: Call for comments - pkg_trans

2008-07-31 Thread Michel Talon
Doug Barton wrote: > BTW, I thought of another problem scenario. The user installs port M, > and it brings dependencies D1, D2, and D3. Then the user installs port > N which also has port D2 as a dependency. Then D2 becomes available for deletion only after M and N have been deleted or no more

Re: Call for comments - pkg_trans

2008-07-31 Thread Doug Barton
Ivan Voras wrote: Doug Barton wrote: You have some very interesting ideas there. Not that I want to dissuade you in any way from doing this, but I would like to point out that portmaster already does some of what you're suggesting and it could fairly easily be modified to do just about all th

Re: Problems with portupgrade && xscreensaver-gnome

2008-07-31 Thread Doug Barton
Bill Moran wrote: Understood. But keep in mind that this was not an error, it was a warning. Perhaps the ports infrastructure doesn't differentiate between those two as much as I think. The use of the make .warning trick is deprecated in the ports tree precisely because it leads to confusion

Re: Call for comments - pkg_trans

2008-07-31 Thread Michel Talon
Ivan Voras wrote: > I apologize in advance if what I'm trying to do seems stupid or it > has=20 > already existed since the Dawn of Time (i.e. when McKusick was in=20 > diapers) but I'd like your comments on this idea: > > http://wiki.freebsd.org/IvanVoras/PkgTransProposal > > I can write the p

Re: Call for comments - pkg_trans

2008-07-31 Thread Miroslav Lachman
Ivan Voras wrote: Doug Barton wrote: You have some very interesting ideas there. Not that I want to dissuade you in any way from doing this, but I would like to point out that portmaster already does some of what you're suggesting and it could fairly easily be modified to do just about all th

Re: Call for comments - pkg_trans

2008-07-31 Thread Ivan Voras
Doug Barton wrote: You have some very interesting ideas there. Not that I want to dissuade you in any way from doing this, but I would like to point out that portmaster already does some of what you're suggesting and it could fairly easily be modified to do just about all the rest of it. The t

Re: Problems with portupgrade && xscreensaver-gnome

2008-07-31 Thread RW
On Thu, 31 Jul 2008 08:16:28 -0400 Bill Moran <[EMAIL PROTECTED]> wrote: > In response to Doug Barton <[EMAIL PROTECTED]>: > > > For the same reason that portmaster dies on errors, neither program > > is omniscient. :) If ports tools hit a point where it's not clear > > how to proceed they _sho

Re: Call for comments - pkg_trans

2008-07-31 Thread Ivan Voras
Jeremy Chadwick wrote: On Thu, Jul 31, 2008 at 06:25:27AM +0200, Ivan Voras wrote: Hi, I apologize in advance if what I'm trying to do seems stupid or it has already existed since the Dawn of Time (i.e. when McKusick was in diapers) but I'd like your comments on this idea: http://wiki.fre

Re: Problems with portupgrade && xscreensaver-gnome

2008-07-31 Thread Marcin Wisnicki
On Wed, 30 Jul 2008 17:42:33 -0500, Jeremy Messenger wrote: > On Wed, 30 Jul 2008 17:09:11 -0500, Marcin Wisnicki > <[EMAIL PROTECTED]> wrote: > >> If .warning breaks portupgrade I can change it to IGNORE. > > I prefer remove .warning and IGNORE. If user wants to enable keyring > then the WITH_K

Re: Problems with portupgrade && xscreensaver-gnome

2008-07-31 Thread Bill Moran
In response to Doug Barton <[EMAIL PROTECTED]>: > Bill Moran wrote: > > It's a combination of a number of issues: > > 1) The ports infrastructure shouldn't let you set options that don't make > >sense. > > I think that one could argue that it should be _hard_ to set options > that "don't ma