[Gimp-developer] gimp-perl moved into its own CVS module
Hi, when I saw your mail, I remembered that I haven't yet told you that we finally moved gimp-perl out of the gimp HEAD branch into its own CVS module called gimp-perl. Hoepfully someone will find the time to resurrect its functionality and make it work with GTK+-2.x and GIMP-1.3. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Wed, Feb 26, 2003 at 07:56:05PM +0100, Sven Neumann <[EMAIL PROTECTED]> wrote: > when I saw your mail, I remembered that I haven't yet told you that we > finally moved gimp-perl out of the gimp HEAD branch into its own CVS > module called gimp-perl. Hoepfully someone will find the time to > resurrect its functionality and make it work with GTK+-2.x and > GIMP-1.3. Well, I must admit that I am not really keen on working on gimp-perl in gimp-cvs anymore, anyways. The continuous mobbing made the air somewhat bigheaded up there. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
Hi, writes: > Well, I must admit that I am not really keen on working on gimp-perl in > gimp-cvs anymore, anyways. The continuous mobbing made the air somewhat > bigheaded up there. Marc, there has been no mobbing going on (despite your continous ranting perhaps). There are two reasons for moving gimp-perl into a separate module: (1) It doesn't work with GIMP-1.3 and noone seemed to work on getting this fixed. Since we want to release soon, we were forced to do something. Having gimp-perl in a seperate module allows to have it maintained independently of the main GIMP package. (2) There are a couple of severe problems with the build that have been outstanding for a very long time and noone did anything about them. In particular I'm speaking of: http://bugzilla.gnome.org/show_bug.cgi?id=20052 http://bugzilla.gnome.org/show_bug.cgi?id=35694 http://bugzilla.gnome.org/show_bug.cgi?id=79751 http://bugzilla.gnome.org/show_bug.cgi?id=81791 http://bugzilla.gnome.org/show_bug.cgi?id=104726 I expect that some of these problems are more easily fixed in a separate module since integration of the perl build environment into the GIMP build environment has proven to be non-trivial. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 11:12:57AM +0100, Sven Neumann <[EMAIL PROTECTED]> wrote:
> Marc, there has been no mobbing going on (despite your continous
Just about every of your mails you wrote that has anything to do with
gimp-perl contains some (usually little) amounts of FUD. It might not be
intentional, but it's scary that people like you have the need for this.
If you feel that I am ranting unwarranted then I cannot help you.
Despite me telling you a lot olf times ("rants"), you continue spreading
FUD. Since I regard you as the main gimp developer right now, I take this
as an official sign to really go away.
I mean, I told you... you give a shit and continue... What else can I do
to make you behave less anti-social?
> ranting perhaps). There are two reasons for moving gimp-perl into a
> separate module:
I don't question these reasons at all, btw. Moving gimp-perl, however, is
not the reason why I felt mobbed at all.
> (2) There are a couple of severe problems with the build that have
I didn't know this (but I don't use the bugtracker, since despite a lot of
tries I never got an account there, so it's rather useless for me).
> I expect that some of these problems are more easily fixed in a
> separate module since integration of the perl build environment
> into the GIMP build environment has proven to be non-trivial.
Well, this is true, but this is also partly because people who go in and
change things fix most of the plug-ins but don't even attempt to do a
one-line variable change inside gimp-perl.
--
-==- |
==-- _ |
---==---(_)__ __ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
Hi, writes: > > (2) There are a couple of severe problems with the build that have > > I didn't know this (but I don't use the bugtracker, since despite a lot of > tries I never got an account there, so it's rather useless for me). it seems we suffer from the same problem: I've told you about these problems several times and it seems you forgot about it. So did I forget that there was a problem calling Script-Fu from anything but Script-Fu. Perhaps us two just have too many things to care about... Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 06:07:22PM +0100, Sven Neumann <[EMAIL PROTECTED]> wrote: > Hi, > > writes: > > > > (2) There are a couple of severe problems with the build that have > > > > I didn't know this (but I don't use the bugtracker, since despite a lot of > > tries I never got an account there, so it's rather useless for me). > > it seems we suffer from the same problem: I've told you about these > problems several times and it seems you forgot about it. It seems this is wrong and only you forgot about it. I went through all bug reports you ever told me about and fixed, or at leats tried to fix them in good faith. I remember having given you feedback on them, too, but maybe in the last year or so some mails slipped through, I don't know. > forget that there was a problem calling Script-Fu from anything but > Script-Fu. Well, you keep forgetting it, don't you? In any case, arguing about open bug reports (that are long fixed) isn't going to get us anyhwere. > Perhaps us two just have too many things to care about... Perhaps. But I don't go out in the public and keep claiming wrong things when I _know_ that I _do not_ know. http://bugzilla.gnome.org/show_bug.cgi?id=20052 This bug report is rather outdated and supposedly fixed since MANY years. http://bugzilla.gnome.org/show_bug.cgi?id=35694 Same issue here. http://bugzilla.gnome.org/show_bug.cgi?id=79751 Oops, this is certainly not something you told me about ever. http://bugzilla.gnome.org/show_bug.cgi?id=81791 This also is rather valid - I missed the change from overwriting prefix to destdir. http://bugzilla.gnome.org/show_bug.cgi?id=104726 Well, this is another case of broken compilation environment (gcc doesn't support the native asm syntax and compiler switches). In any case, the two bugs are really easy to fix - I don't think you ever told me about those. Yes, it's not at all your duty to tell me about these - I am not at all arguing about that, or wanting you to invest even more time and work. My problem is that you are investing too much time with misinformation - something that is relatively easy to avoid, especially since I do tell you about this regularly (oh sorry, for you it's ranting - no wonder you keep ignoring it). -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, 28 Feb 2003 16:19:01 +0100, <[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> wrote: > > (2) There are a couple of severe problems with the build that have > > I didn't know this (but I don't use the bugtracker, since despite a lot of > tries I never got an account there, so it's rather useless for me). Strange. I had no problem creating an account some time ago: http://bugzilla.gnome.org/createaccount.cgi Submitting your e-mail address using this form is the only thing you need to be able to add comments to any bug report. If you also want to be able to confirm bug reports, to close them or to re-assign them, then you should send a request to [EMAIL PROTECTED] after you account has been created. It may take a couple of days before this request is honored, but in the meantime you can already use your account to add your comments in any bug report. -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
Hi, writes: > http://bugzilla.gnome.org/show_bug.cgi?id=20052 > > This bug report is rather outdated and supposedly fixed since MANY years. Now closed at your request. > http://bugzilla.gnome.org/show_bug.cgi?id=35694 > > Same issue here. Same here. > http://bugzilla.gnome.org/show_bug.cgi?id=79751 > > Oops, this is certainly not something you told me about ever. I certainly did; I even added your email to the Cc: which should have caused bugzilla to send you an email about it. > http://bugzilla.gnome.org/show_bug.cgi?id=81791 > > This also is rather valid - I missed the change from overwriting > prefix to destdir. If you ever come around to fix this, will you please notice us about your change so we can avoid to have the bug-report open for some more years. > http://bugzilla.gnome.org/show_bug.cgi?id=104726 > > Well, this is another case of broken compilation environment (gcc doesn't > support the native asm syntax and compiler switches). Now closed as invalid. > Yes, it's not at all your duty to tell me about these - I am not at all > arguing about that, or wanting you to invest even more time and work. I'm sure you know how to query Bugzilla for the gimp-perl component of the gimp module. Salut, Sven PS: Thanks to the three bugs closed due to our little flame-war we are now down to rank 7 in the Bugzilla Hall of Shame (http://bugzilla.gnome.org/weekly-bug-summary.html). Thanks! :-) ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On 28 Feb 2003, at 18:35, Raphaël Quinet wrote: > On Fri, 28 Feb 2003 16:19:01 +0100, <[EMAIL PROTECTED] ( Marc) (A.) > (Lehmann )> wrote: > > (2) There are a couple of severe problems with > the build that have > > I didn't know this (but I don't use the > bugtracker, since despite a lot of > tries I never got an account > there, so it's rather useless for me). > > Strange. I had no problem creating an account some time ago: > http://bugzilla.gnome.org/createaccount.cgi > Submitting your e-mail address using this form is the only thing you > need to be able to add comments to any bug report. If you also want > to be able to confirm bug reports, to close them or to re-assign them, > then you should send a request to [EMAIL PROTECTED] after you > account has been created. It may take a couple of days before this > request is honored, but in the meantime you can already use your > account to add your comments in any bug report. I vaguely remember that Bugzilla needed JavaScript or Cookies or some other extra technology to be enabled before you could use it. It's not set-up very well. -- branko collin [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 06:35:26PM +0100, Raphaël Quinet <[EMAIL PROTECTED]> wrote: > Strange. I had no problem creating an account some time ago: > http://bugzilla.gnome.org/createaccount.cgi Well, I registered a long time ago (I think under a differrent URL). The problem is: > then you should send a request to [EMAIL PROTECTED] after you account I originally was referred to martin baulig (I think), and tried to contact him, to no avail (yes, that's years ago). The I was refrred to one other person (who also didn't respond). I also tried the above address, but nothing happened, either. I might try again (and would probably succeed eventually), but I tried once a year in vain (not last year), and I am somewhat... tired :() You know, I am really frustrated by this "developer community". I would have hoped that people like sven (or you, even if it's not your intent) eventually would stop their (mild) perl-bashing, but it's not at all fun to try to dveelop within a community that shows you again and again that they don't care for your project, spread misinfirmation (wether by intent or not), and generally aren't helpful. Really, claiming gimp-perl is broken despite soo many people using and relying on it for years _was_ wearing me out. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 08:30:09PM +0100, Branko Collin wrote: > > I vaguely remember that Bugzilla needed JavaScript or Cookies or some > other extra technology to be enabled before you could use it. It's > not set-up very well. Just another FUD example. You don't need JS (though it may improve user experience in a few places). You need cookies to log in, so you generally need cookies to change anything (what brower do you use? bugzilla works even in lynx). You don't need anything to search for bugs, wget is enough if you know what you are searching for. Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 07:30:35PM +0100, Sven Neumann <[EMAIL PROTECTED]> wrote: > > http://bugzilla.gnome.org/show_bug.cgi?id=79751 > > > I certainly did; I even added your email to the Cc: which should have > caused bugzilla to send you an email about it. Hmm.. well, then it was as I said and I didn't notice it (however, it really wasn't repeatedly...) > > http://bugzilla.gnome.org/show_bug.cgi?id=81791 > > If you ever come around to fix this, will you please notice us about I just checked in this one-line change. If it really all that was required, then it's solved now and could be closed. > PS: Thanks to the three bugs closed due to our little flame-war we are > now down to rank 7 in the Bugzilla Hall of Shame > (http://bugzilla.gnome.org/weekly-bug-summary.html). Thanks! :-) Well, nobody said it's totally useless to quarrel sometimes, at least there is the chance of getting somrthing moving again... Hmm.. rank 6 will be difficult to reach, though. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
On Fri, Feb 28, 2003 at 10:07:30PM +0100, Marc A. Lehmann wrote: > On Fri, Feb 28, 2003 at 09:19:17PM +0100, "David Necas (Yeti)" <[EMAIL PROTECTED]> > wrote: > > You need cookies to log in, so you generally need cookies to > > change anything (what brower do you use? bugzilla works even > > in lynx). > > Well, certainly lynx doesn't send cookies if you tell it not to. I don't > know a browser that always sends cookies, anyways. > > (Yes, you know that, but assuming that everybody happily lets himself > monitor using cookies is not reflecting reality ;) It's OT, but you started about reality: Default lynx behaviour is to ask about each cookie. You can decide to accept exactly the log-in one (it sends a few more). You can make sure it's deleted after session. You can then set your cookie preferencies in the config. The reality is, you have to prove yourself to make any changes, and this is a very logical requirement. The stronger authentization, the better you are monitored. You can't be monitored less. If you are so paranoiac you don't accept cookies from bugzilla.gnome.org, then I can't understand why you bother to read any mail not signed by some trusted GnuPG key (namely gimp-dev), not speaking about responding to them. We are probably all evil hackers monitoring your mailing behaviour. Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
> It's OT, but you started about reality: I didn't start anything. A very important rule to follow on the 'net or anywhere else: do _NOT_ forward private mails to public forums. ;) > bugzilla.gnome.org, then I can't understand why you bother > to read any mail not signed by some trusted GnuPG key > (namely gimp-dev) Did I say anything about that issue? Maybe I really do bother... I regularly have problems explaining to people why a gpg key that is not signed or verified by anybody (self-signature not counted) is still very useful and still has all the same identification qualities as a "trusted" (or better: verified by showing your ID card) gpg key. (A trusted key, btw, is something that actually _weakens_ your security. If you are paranoic you should never trust _any_ key. And as a general rule of thumb: if you trust anybody or anything, you are not really paranoic ;) > not speaking about responding to them. We are probably all evil hackers > monitoring your mailing behaviour. Well, that's probably not true, but wether I am paranoic or not, I _do_ respect it when people send me private (off-topic) mails and don't forward them... F'up in private again, please ;) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl moved into its own CVS module
fre 2003-02-28 klockan 18.28 skrev [EMAIL PROTECTED]: > http://bugzilla.gnome.org/show_bug.cgi?id=79751 > > Oops, this is certainly not something you told me about ever. The "bug activity" log for this report (available as a link from the page) very clearly shows that [EMAIL PROTECTED] added a cc: to [EMAIL PROTECTED] for this bug report almost a year ago, 2002-04-24... ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
