RSS
 

Enlightenment Fedora RPM Repo - updated

23 Nov

So i updated the packages again and you can get the elf library 1.7.2 with enlightenment alpha 4. I also added in terminology.

You will need to use the same repo. And sorry this is only for x86_64 systems right now.

cat /etc/yum.repos.d/Enlightenment.repo
[Enlightenment]
name=Enlightenment for Fedora $releasever
baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever
enabled=1
metadata_expire=7d
gpgcheck=0

So enjoy!

 
0 comments

Posted ed_mann in Open Source

 

Enlightenment Fedora RPM Repo

21 Nov

So i have been holding out on people in having an easy way to try out Enlightenment  on their Fedora 17 systems. I wrote a very generic and non-error checking script to build Enlightenment and the Enlightenment Foundation Libraries. I have been using this method to update my work and home machines and not having to build on two different systems. Also if i tired it on one and it did not work i then did not update the second system.

I do my builds on a vm instance of Fedora 17. That way if i wreck it it's an easy recovery from a snapshot i do before the build. So here is the repo info you will need to use the packages i have built. I have not gpg signed these packages. I have the docs on how to do it and i will get it done if i get a response that people will actually be using this repo.

 

cat /etc/yum.repos.d/Enlightenment.repo
[Enlightenment]
name=Enlightenment for Fedora $releasever
baseurl=http://edmann.com/Enlightenment/repo/Fedora/$releasever
enabled=1
metadata_expire=7d
gpgcheck=0

 

I was planning on pinging the manager for Enlightenment on the Fedora project, i have just been to busy to get around to it.

Please let me know if this is repo is usefull to you. I should also post a screenshot or a video or something to show how nice e17 really is. The new default theme in alpha3 is really nice, there is currently some problems with building alpha4. From the mailing list they are working on how to resolve this.

 
0 comments

Posted ed_mann in Open Source

 

Chuck Woolery on Assult Rifles

13 Nov

This is a interesting video by Chuck Woolery about assult rifles. Enjoy.

 
0 comments

Posted ed_mann in Constitution

 

Migrating from gitolite to gerrit

09 Nov

So i have been working more and more... or trying at least with gerrit and was having some issues. Well my problem was i was using gitolite. Gitolite has some hooks  that would need to be removed from the project before you could use gerrit and commit changes. Below are my notes, use at your own risk. Not that you would lose anything, you back everything up right?! :-D

 

Remove Gitolite hooks

Just remove these files from your project. This is on the master server that has you git repo. go into the projects hook directory and then

[gerrit@git my_project.git ]$ rm -f gitolite-hooked gl-pre-git.hub-sample post-receive.mirrorpush update update.secondary.sample

Fixing permissions

So after i removed the hooks i still needed to fix permissions. I don't fully understand gerrit, however i was able to do this to allow me to change the permissions without a review. This may be wrong, however it works for me and until i learn otherwise i will continue to do it.

Create tmp directory

Create a temporary directory and do a git init inside it

[gerrit@git sandbox]$ mkdir tmp

[gerrit@git sandbox]$ cd tmp

[gerrit@git tmp]$ git init

Then pull in the project you want to fix permissions on.

[gerrit@git tmp]$ git pull /data/git/repositories/my_project.git refs/meta/config

This will give you the files that you will want.

Note: You will need to visit the project once in gerrit to get it to create the generic "config" files

Setting permissions

Create a new file called groups. In that file add the Group UUID and Group Name

# UUID                                          Group Name #
c5a45e67f3d27518770bb3810f4bf02bef2739fb        Administrators

You can find your group UUID and name in the gerrit site under Group->List->Administrators->General The UUID will be at the top of the page.

Save that file and then edit the project.config file. Make it look something like the following.

[access "refs/heads/*"]
        push = group Administrators
        owner = group Administrators
        pushMerge = group Administrators
        exclusiveGroupPermissions = pushMerge
[project]
        description = My Test project
        state = active

Now add the two new files with git add and then commit with comment. I should not need to tell you how to do that, if i do i will hear about it in the comment section below. Once you are done that the final step is to push this all back up into the project.

[gerrit@git tmp]$ git push /data/git/repositories/my_project.git/ HEAD:refs/meta/config

That's all it takes. You are good to go now. You should be able to push changes to your project hosted by gerrit.

 
0 comments

Posted ed_mann in Computers & Technology