(old)Puppy Linux Discussion Forum

Without adding any deps to the install, it should be possible to write our own perl files to use as headers for git, which is a website frontend for Git.

why bother? Well, at Github.com, you can sign up and upload your SSH key over the web interface, making it much simpler for beginners to do it.

We could easily write our own little PERL script include it at the top of the page (cgit allows this easily) and use it to provide users with a really easy way of getting involved in proper collaborative style puppy projects..


The header could include:

- an upload form + backend to add your SSH key to the server
- useful link(s) to Git, Puppy and general Linux help
- better, puppy specific theming


Note, this might sound pointless, but updating git is easy, then it's much better, gives an interactive, secure shell, and Cgit works great and is tiny - I will be adding the latest Git and Cgit to the akita devx...

... I see no reason why puppy should not have latest git+cgit in the devx.. git hasn't grown much (latest i compiled was 8mb), and cgit is about 370kb..


So... Here's the question...

How in PERL do you add stuff to files on the file system, and manage file/dir ownership and permissions?

And what is the easiest way in PERL of managing user registrations?

sc0ttman wrote:Without adding any deps to the install, it should be possible to write our own perl files to use as headers for git

I guess you mean to say cgit here. But I still don't follow what you're actually suggesting to use cgit for...

disciple wrote:

sc0ttman wrote:Without adding any deps to the install, it should be possible to write our own perl files to use as headers for git

I guess you mean to say cgit here. But I still don't follow what you're actually suggesting to use cgit for...

yes i did mean cgit there,,, and my point is (just thinking out load) that it should be quite easy to include a mini github inside the devx (using git+cgit+custom header) , and then users could start serving their projects through git+web, using their fave puppy, much more quickly and easily.. it would encourage users to develop and collaborate on puppy projects in that way, or at least make it a bit faster and easier..

I don't understand why users would want to serve their own projects rather than using GitHub or something.

disciple wrote:I don't understand why users would want to serve their own projects rather than using GitHub or something.

then don't worry about it

Obviously you think the idea is worth putting effort into, and You said you can see no reason not to do it - I just thought you might want to explain the reason to do it.

disciple wrote:Obviously you think the idea is worth putting effort into, and You said you can see no reason not to do it - I just thought you might want to explain the reason to do it.

ok, but i believe i already stated above that i think it's a very easy update for a dev to make in the devx of any future pups, so that the end users of those future pups can get started much easier with git hosting if they wish.. the 'effort' to do it is relatively tiny, but I'm not a puppy dev, so i'm not in control of what goes into the devx of any given puppy.. so i thought i'd just 'put it out there'..

Scott, why not consider fossil? It is only 4MB uncompressed (on 64-bit, could be smaller on 32-bit) and it has everything already. For those who loves git they can always convert between the two: http://www.fossil-scm.org/xfer/doc/tip/www/inout.wiki.

jamesbond wrote:Scott, why not consider fossil? It is only 4MB uncompressed (on 64-bit, could be smaller on 32-bit) and it has everything already. For those who loves git they can always convert between the two: http://www.fossil-scm.org/xfer/doc/tip/www/inout.wiki.

I thought about it.. and maybe I am missing something, but the git package in wary (and therefore the akita devx) is around 50mb, and the latest i compiled (without extras, perl, python, etc) was 8mb, i compared, the difference was the git stuff in /usr/libexec/ .. yet to fully compare features and build a new devx with the new git, but i'm *hoping* to go that way, save space... like I say, maybe I am missing something there...

..a side thought.. I know generally there is not much love for git and such in puppy dev land, and its not used in many puppy projects, but maybe if we did it a bit more, and also included better git support in puppy, we might attract more devs from elsewhere...