From: Andreas K. <and...@ac...> - 2015-05-06 21:46:57
|
On Wed, May 6, 2015 at 1:48 PM, Damon Courtney <da...@tc...> wrote: >> I will make an account for you. Commit access. Please use branches for >> new code. Any special wishes regarding the account name ? > > > I always just go by damon (or Damon if that’s the convention) or > damoncourtney. I find very people named Damon, so I can generally get by on > just the first name. :) damon it is. Done. Initial password is "startup". Login page is https://core.tcl.tk/tcllib/login After a login the same page offers logout and password change. > I’ve written multiple VFS layers to deal with archive files, but that’s not > this. This is a straight-up utility package for zip files on the order of: > > set fp [::zip::open foo.zip w] > ::zip::add $fp some_file.txt > ::zip::delete $fp some_other_file_in_the_zip.txt > ::zip::close $fp > etc… Similar to what Sean is writing ion the odie branch, I think. > So, expanding on the thing I rattled off a little earlier, what if we just > built a system around Github (that could be replaced with some other system > in the future)? I will not stop you. (You asked why fossil was used over git(hub). The people advocating fossil did the work of converting the CVS, and tickets, ... The advocates for git(hub) advocated). > Then, I wouldn’t need commit access to get my packages in, I > would just need approval to get my package added to the list (or not, > depending on what the user has chosen). > I could foresee a repo at github.com/tcltk/packages that just contains an > index detailing packages and where to find them. How would that repo work ? Some markdown file README/.md holding the links and getting updated ? Some more machine-usable db file for the links, with the index generated from that ? > Most would probably live on > Github, but it wouldn’t be difficult to support other platforms. Sadly, > supporting our own core.tcl.tk would be the hardest since I don’t think > Fossil has a proper API behind it. Not sure what your 'proper API' would have to provide. As such I cannot say if fossil supports that or not. Fossil does have an integrated webserver. List of pages etc. available via https://core.tcl.tk/tcllib/help It can be compiled with json support which provides more web pages. > Luckily, all the major repos are mirrored > to Github already anyway. > Github’s API is dead simple. Get a list of releases to get package versions, > get the latest if no version is given. Speaking of, why doesn’t tcltk/tcllib > have any proper releases? Ah ... https://core.tcl.tk/tcllib/timeline?n=50&y=e&v=0 >From the tagging POV, each release has 2 tags "release", and a tag indicating the version, like "tcllib-1-17" > It has tags, which this package manager could use > in place of releases, but the releases mechanism seems a bit more purposeful > since you’re actually designating a final thing. Can you point me to documentation regarding this release mechanism (of github) ? I am not sure why tags cannot designate a final thing?! > > That might actually work. Who admins github.com/tcltk? jeff, sebres, pat, das, myself > > D -- % Tcl'2015 Oct 19-23 = http://www.tcl.tk/community/tcl2015/cfp.html % EuroTcl'15 June 20-21 = http://www.eurotcl.tcl3d.org/ Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ F: 778.786.1133 and...@ac..., http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato |