Since the new vpackager will have a GUI for cruxports....Is anyone else interested in creating our very own ports repository?We could use this to build or very own distro-specific stuff (maybe the stuff that you're advised not to build from slack)?Could also include ports to build stuff like what blurymind was suggesting ... dynamic scripts... only instead of a script repo it would be ports. Using the backend and front end we already have.Of course, we can also offer ports to build newer versions of other applications as well...

I'd like to get everyone's opinion and reaction to this... and see how many would be willing to help...This would need maintenance as well.

well, i suggested the repo,because then vec community will have more control over its own repo- we will be able to fix non-working scripts...add scripts..have a way for vlpackager to collect information from its own community's database (like a way to warn the user of ports that are known not to work)

I like the idea of scripts that build from git,cvs,svn.. because the code there is alive and you get the latest, edgy stuff. Moe sent me such a script a while ago that builds compiz and i thought that it is pretty nifty,because latest compiz usually has most bugfixes and additional new plugins.Specially for some applications it is sometimes best to get the latest source..I called this kind of ports "dynamic",because the source there is changing and they dont need to be updated and are avaiable (pretty nifty).Some weeks ago i got latest gimp from svn through a process that can be easily automated via a script and i found it to be very stable,not to mention all the sweet new features it has..Another example for niftiness of scripts that build from cvs/svn is wine. Wine is under rapid development and every week a new version comes out with lots of patches applied to it.I personally like to have latest wine and submit information to winehq about what works and what not (if everything changes/breaks).I think that it is still early to see how things develop,but i really do think that what is done here is very exciting.

gbr2: error while loading shared libraries: libgnuintl.so.8: cannot open shared object file: No such file or directoryi tried after installing gettext from sw12 official repo and running ldconfig, i get the same error.

This is perfect! I read through the other thread you had on this and I definitely see this becoming the standard method for installing software from source. I know it's still a work in progress but this is what I would have wanted as a beginner (meaning I still want it).

Quote

I've been adding stuff to the wiki and updating the screen shots. vvucic will also be helping me with the wiki... so go ahead.. check that out too

I think you should spin off your section of the " How to install software from source code" into a separate article. Just link to your how to from mine from its present position in the document. That way someone who does not want to install from the command line but winds up in my how to can find yours. Perhaps I should rename mine to "How to install source code from the command line". Do you want those images from the top of this thread in your wiki article?

If you want I will make those changes for you. Unless of course you and vvucic have other plans."VPACKAGER the VL 6.0 source code installer" sound okay for a title?

This could be a major turning point for how software gets installed. Keep up the good work!

I am not sure what I need a GMAIL account for. If it's for the wiki articles I do not. Although I would not mind being more involved in it, I am somewhat unreliable for things that require timely attention.If you just want to mail me new features and pictures to be included in the wiki, sure. But the above shortcoming still applies. vvucic is probably a better bet. But I will help if I can.

1 I did not use all of your pictures because I was not sure where to put them. If you want to add them2 just put your cursor on the edit page where you want them.3 click the picture frame on the bar above the editing area4 upload your picture when the upload window appears5 double click on the uploaded picture that appears in the same window

and your done. Your picture will appear in the wiki right where your cursor is.