From noreply at rubyforge.org Fri Jun 26 18:18:26 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 26 Jun 2009 18:18:26 -0400 (EDT) Subject: [Facets] [ facets-Feature Requests-26437 ] git versions Message-ID: <20090626221826.87E591678297@rubyforge.org> Feature Requests item #26437, was opened at 2009-06-27 00:18 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26437&group_id=804 Category: None Group: None Status: Open Priority: 3 Submitted By: Marc Dequ?nes (duck) Assigned to: Nobody (None) Summary: git versions Initial Comment: Please tag the release commits, so it is easier to compare versions and work with your source. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26437&group_id=804 From noreply at rubyforge.org Fri Jun 26 18:27:25 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 26 Jun 2009 18:27:25 -0400 (EDT) Subject: [Facets] [ facets-Feature Requests-26438 ] Please provide a suitable tarball for packagers Message-ID: <20090626222725.A39141678297@rubyforge.org> Feature Requests item #26438, was opened at 2009-06-27 00:27 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26438&group_id=804 Category: None Group: None Status: Open Priority: 3 Submitted By: Marc Dequ?nes (duck) Assigned to: Nobody (None) Summary: Please provide a suitable tarball for packagers Initial Comment: Gems were made to solve a few issues, and mostly to solve management on systems with bad or unexisting packaging software, but this is not true for most UNIX systems; mixing several package managers is quite a mess. I intend to create a Debian package of your software, but having gems is mostly useless for building a package. Then, i've got 2 options: packaging using the lastest released tarball (2.4.1), which is more than 1 year old, and which would probably be useless with recent applications, or use a git snapshot, but i guess you would not be that happy when people would bug you about an unfinished software version. I've then decided to look at the git snapshot at the moment, in order to get a working version and have nice applications like webgen working, filling an important gap. If you're interrested in helping us distribute your software, then consider providing a tarball again. More generally, i would advise you to have a look at the following page to understand our problems: http://pkg-ruby-extras.alioth.debian.org/upstream-devs.html . Thanks ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26438&group_id=804 From noreply at rubyforge.org Fri Jun 26 21:40:49 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 26 Jun 2009 21:40:49 -0400 (EDT) Subject: [Facets] [ facets-Feature Requests-26441 ] License conflict with htmlfilter Message-ID: <20090627014053.9C0F4167829F@rubyforge.org> Feature Requests item #26441, was opened at 2009-06-27 03:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26441&group_id=804 Category: None Group: None Status: Open Priority: 3 Submitted By: Marc Dequ?nes (duck) Assigned to: Nobody (None) Summary: License conflict with htmlfilter Initial Comment: Unfortunately, 'lib/more/facets/htmlfilter.rb' is licensed under Creative Commons Attribution-ShareAlike 2.5 License, which requires that "If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.". The "or similar license to this one" does not mean anything clear, but if i guess the conditions of the Ruby License are quite similar, the conditions of the GPL is not because far more restrictive. Most of the code licensed under GPL is also licensed using the Ruby license, but not all ('lib/more/facets/linkedlist.rb' for example), so this render this file incompatible with the software as a whole. Moreover, the "build upon this work" condition may forbid using this library with a GPL software too (but the wording is far from being clear). Please relicense or remove this file. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3172&aid=26441&group_id=804 From noreply at rubyforge.org Sun Jun 28 03:30:54 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 28 Jun 2009 03:30:54 -0400 (EDT) Subject: [Facets] [ facets-Bugs-26446 ] __HERE__ can not work. Message-ID: <20090628073054.A04F3185810C@rubyforge.org> Bugs item #26446, was opened at 2009-06-28 17:30 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3169&aid=26446&group_id=804 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: William Mason (william) Assigned to: Nobody (None) Summary: __HERE__ can not work. Initial Comment: The facets kernel extension __HERE__ is based on a false premise that it would show you the line of code that it is called from. At least that is how it "appears". Of course when I thought about it, all it can ever do is report its OWN file name and line number. So a line like ... puts " * Exception in #{self.name.to_s}, (#{__HERE__})." Can only ever, always emit: * Exception in someclass, (... lib/ruby/gems/1.8/gems/facets-2.5.2/lib/core/facets/kernel/__here__.rb: 4). The __HERE__ idea is a really good one, this isn't a way to implement it. At the very least the existing implementation should use the Caller method and report the caller for the function. That at least would give a good shot at a more effective answer. Otherwise remove it from Facets and document that it is not workable. w. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=3169&aid=26446&group_id=804