#16434: Package d3.js
-------------------------------------+-------------------------------------
       Reporter:  tmonteil           |        Owner:  tmonteil
           Type:  enhancement        |       Status:  needs_info
       Priority:  major              |    Milestone:  sage-6.3
      Component:  packages:          |   Resolution:
  optional                           |    Merged in:
       Keywords:  d3.js              |    Reviewers:
        Authors:                     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  85c4ce7fd63d638545e65e05e73d7c84a2cc0e72
  u/tmonteil/package_d3_js           |     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by ncohen):

 Yoooooooo !

 > Hi Nathann and thanks for caring,

 My pleasure. I am so sick of watching all my patches in needs_review and
 all the code I have yet to submit stuck because of endless nitpicking that
 I am actually glad to participate to some honest work... `>_<`

 > it is fun that i asked myself all those questions yesterday night, and i
 > could not find an answer within the existing spkgs or the doc (another
 was
 > whether i should call the spkg d3, d3js or d3_js).
 >
 >     find -name spkg-src -exec echo '{}' \; -exec cat '{}' \; | less

 Hey by the way... Once a student of mine showed me a different way to do
 stuff like that, which is actually MUCH more powerful :

 {{{
 find . -iname "spkg-src" | while read line; do echo $line; cat $line; done
 }}}

 > There seem to be no rule concerning the spkg-src script. The patterns
 you
 > may discover between some of the spkg-src scripts only come from the
 fact
 > that pieces are copied from one to another.

 Okayokay.

 > remove a single subdirectory). I could create a src/ directory within
 the
 > work/ directory, this would make sense, but since the tarball contains
 > only two files ('d3.min.js' and 'LICENSE') i didn't think it was worth
 > putting them in a separate directory before creating the tarball, but it
 > is possible if you think it may help.

 Well, I see no reason, you did the work right...

 > Actually, autotools spkg-src already puts its tarball in the upstream/
 > directory.

 I see. Could you use SAGE_ROOT/upstream instead of ../../../../ btw ? I
 did this kind of things a long time ago and several generations of release
 managers cursed me for it `:-P`

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/16434#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to