Attached are spec files for building rpms for moblock-control 1.0 and moblock 0.9 rc2. These have been successfully tested on Fedora Core 9.

Feel free to suggest improvements.

Attached Files

	moblock.spec.gz (807 Bytes, 24 views)
	moblock-control.spec.gz (1.5 KB, 12 views)

Attached is the updated moblock-control spec file for moblock-control 1.2. Again, tested on Fedora Core 9.

Attached Files

moblock-control.spec.gz (1.5 KB, 17 views)

Sorry for being daft...but where exactly can I download
the moblock-0.9~rc2.tar.gz referred to in the .spec file.

I grabbed
and renamed it to moblock-0.9~rc2.tar.gz However, it didn't contain the necessary
patches
e.g.
Thanks for your help. I will be building this on Fedora 10. So will report back success or other issues.

I downloaded the tarball from the SCM Repository viewer at:
http://moblock-deb.svn.sourceforge.n...block-0.9~rc2/

Then, choose 'Download GNU tarball' at the bottom.

However, I notice this patch has changed names, so I will post a new .spec file before long.

Thanks...

Any plans to develop a .spec for Mobloquer?
It complied easily on a Fedora 10 box with these steps:
If yes, then do note that a GUI front end to sudo is necessary.
For Fedora 10, then I just grabbed beesu which seemed to do the trick.
If none of the GUI front ends are installed then mobloquer will display
an error message upon startup.

Let me know of I can be of any assistance.

piefreak, I also suggest to apply the other patches to moblock. See here: http://forums.phoenixlabs.org/showpo...36&postcount=5

As you might know, I'm just in the progress of renaming moblock-control to blockcontrol, so you will soon have to make new specs again

For mobloquer packages you may also use the source from moblock-deb.sf.net.

Further I'd suggest that you post your current specs always in post #1. You may also post instructions how to get the tar.gz there, including the svn revision number on which they are based.
Or you may directly attach the tar.gz there, to make sure that sources and spec file match.

Always feel free to make suggestions or ask for help! I very much appreciate your efforts (that's why I made your thread sticky)!

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.

A new spec 0.9rc2-build2 that includes all patches between 30 and 80.
I am not used to rpmbuild

Here is what I did:
[x@server ~]$ rpm --eval '%{_sourcedir}'
/home/x/rpmbuild/SOURCES
[x@server ~]$ mkdir -p /home/x/rpmbuild/SOURCES
[x@server ~]$ cd /home/x/rpmbuild/SOURCES

copy the spec and targz sources here.

...]$ rpmbuild -ba moblock.spec (ba will build the source and binary)
...]$ sudo rpm -Uvh moblock-0.9~rc2-2.fc10.x86_64.rpm (yum would complain about the signature)
...]$ rpmbuild --clean moblock.spec (will clean everything)

Now I have to find the sources for mobloc-control ...
And will update this post soon hopefully

Attached Files

moblock.spec.gz (1.1 KB, 2 views)

What happened with mobloc-control and blockcontrol ?
- for blockcontrol in SVN, there are no more version numbers (I had to add them by hand.)
- Seems like some files disappeared ? (moblock.default)

By the way, I would have prefer to keep the same beginning: like "moblo..." so there are not far away in the directory listing.

For what I understand there are only scripts in blockcontrol ? So it is architecture (32/64b) independent ?

It creates config file for moblock too ? Like /etc/mobloc/mobloc.conf : this is not handled by Moblock ?

It's very close to be released. Basically I just need to adapt mobloquer, but nothing in blockcontrol itself.

Yes, but you can get the next version number from debian/changelog (of course, without the "~preX" part)

Yes, moblock.default was removed. And blockcontrol.main was added. (It's together with blockcontrol.defaults and .lib in /usr/lib/blockcontrol/). These are the changes that you can see in the file names.
Inside, the new /etc/blockcontrol/blockcontrol.conf is to be used like the old moblock.default. While /usr/lib/blockcontrol/blockcontrol.defaults is the old /etc/moblock/moblock.conf. And blockcontrol.main contains the code (but not the variable defaults) from the old .defaults file.

blockcontrol supports MoBlock and alternatively NFBlock, therefore the renaming. I had the feeling that it is better to make a clean cut and separate the projects clearly.
This should stop e.g. the confusion about moblock.conf, see below...
I admit that a new name may make some new trouble, but I hope to win more by the new, clear situation, which should help especially packagers like now you.

Yes.
Yes, /etc/moblock/moblock.conf and e.g. the master blocklist (/var/lib/blockcontrol/guarding.p2p) are only handled directly by blockcontrol.
blockcontrol then starts moblock with the appropriate command line options.

__________________
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.