Re: Up to date rpm spec file

63 views
Skip to first unread message

Keith Rarick

unread,
Apr 14, 2013, 12:00:49 PM4/14/13
to beansta...@googlegroups.com
Does anyone still want to use that RPM spec file?
Would you volunteer to maintain it? Otherwise I'll
have to remove it entirely; I don't have the ability
to keep it up to date.

On Tue, Jul 10, 2012 at 2:30 PM, Vincent Janelle
<randomf...@gmail.com> wrote:
> The RPM spec file that's shipped with beanstalkd seems out of date (still
> tries to use autoconf, etc) - is there a more up to date version?
>
> --
> You received this message because you are subscribed to the Google Groups
> "beanstalk-talk" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/beanstalk-talk/-/uCiNyujWTPEJ.
> To post to this group, send email to beansta...@googlegroups.com.
> To unsubscribe from this group, send email to
> beanstalk-tal...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/beanstalk-talk?hl=en.

Thomas Parrott - Infinity Tracking

unread,
Apr 14, 2013, 12:03:59 PM4/14/13
to beansta...@googlegroups.com
I can help as will need to maintain mine anyway. Since the daemon feature has been removed its harder to run beanstalk on centos as have to run with & char at end to background it. I've found 1.8 just crashes after q while so we are still running 1.4 but will hopefully upgrade to 1.9 if stable.


Thomas Parrott
Technical Director
...............
Get me anywhere
UK 01737 742 641
US 443-842-6362
infinity-tracking.com
...............
Infinity Tracking
To unsubscribe from this group and stop receiving emails from it, send an email to beanstalk-tal...@googlegroups.com.

To post to this group, send email to beansta...@googlegroups.com.

Keith Rarick

unread,
Apr 14, 2013, 12:07:49 PM4/14/13
to beansta...@googlegroups.com
On Sun, Apr 14, 2013 at 9:03 AM, Thomas Parrott - Infinity Tracking
<thomas....@infinity-tracking.com> wrote:
> I can help as will need to maintain mine anyway.

Awesome, can you start by submitting a pull request to bring
the existing file up to date (or replacing it, whatever you feel
is most expedient)?

Thomas Parrott

unread,
Apr 14, 2013, 12:57:27 PM4/14/13
to beansta...@googlegroups.com
Sure no problem, have forked the repo.

What is the issue with it being an autoconf template?

Shall I just create a new file in the pkg dir called beanstalkd.spec
instead?

Thanks
Tom

Thomas Parrott

unread,
Apr 14, 2013, 1:24:52 PM4/14/13
to beansta...@googlegroups.com
I've seen the new beanstalkd.spec in the root in the 1.9 release so will
work on that.

Looks like its going to be fine, but will also add an init script that
the spec will install.

Where shall I put the init file?

Thanks
Tom

Keith Rarick

unread,
Apr 14, 2013, 1:25:19 PM4/14/13
to beansta...@googlegroups.com
On Sun, Apr 14, 2013 at 9:57 AM, Thomas Parrott
<thomas....@infinity-tracking.com> wrote:
> What is the issue with it being an autoconf template?
>
> Shall I just create a new file in the pkg dir called beanstalkd.spec
> instead?

It's not really an autoconf template; it just looks like one.
We keep the version string in tags rather than files.
When I cut a release, I run a script that fills in the version
string from the current tag. The script used to generate a
tarball, but now it makes another commit under its own tag.

You can see how it currently works:
https://github.com/kr/beanstalkd/blob/master/pkg/dist.sh

And you can see a couple of other files that get filled in this way:
https://github.com/kr/beanstalkd/blob/master/pkg/newstail.in
https://github.com/kr/beanstalkd/blob/master/pkg/bloghead.in

Keith Rarick

unread,
Apr 14, 2013, 1:27:17 PM4/14/13
to beansta...@googlegroups.com
On Sun, Apr 14, 2013 at 10:24 AM, Thomas Parrott
<thomas....@infinity-tracking.com> wrote:
> I've seen the new beanstalkd.spec in the root in the 1.9 release so will
> work on that.

You should base your work on the master branch rather than the v1.9 commit.

> Looks like its going to be fine, but will also add an init script that the
> spec will install.
>
> Where shall I put the init file?

Packaging-related files go in pkg.

Thomas Parrott - Infinity Tracking

unread,
Apr 14, 2013, 1:52:02 PM4/14/13
to beansta...@googlegroups.com
K, shall I edit the SPEC file in root or the one in the pkg dir


Thomas Parrott
Technical Director
...............
Get me anywhere
UK 01737 742 641
US 443-842-6362
infinity-tracking.com
...............
Infinity Tracking


----- Reply message -----
From: "Keith Rarick" <k...@xph.us>
To: "beansta...@googlegroups.com" <beansta...@googlegroups.com>
Subject: Up to date rpm spec file

Keith Rarick

unread,
Apr 14, 2013, 2:45:24 PM4/14/13
to beansta...@googlegroups.com
On Sun, Apr 14, 2013 at 10:52 AM, Thomas Parrott - Infinity Tracking
<thomas....@infinity-tracking.com> wrote:
> K, shall I edit the SPEC file in root or the one in the pkg dir

The one in the root is automatically generated from the one
in the pkg dir, so please edit the source file.

Thomas Parrott - Infinity Tracking

unread,
Apr 15, 2013, 3:38:55 AM4/15/13
to beansta...@googlegroups.com
OK got it, will do.

Thanks

Kind regards

Thomas Parrott
Technical Director
UK 01737 742641
US 443-842-6362

 Infinity Tracking 
Service Portal
infinity-tracking.com/service/ 
Our Service Portal has a comprehensive list of How To Guides and FAQs
Service Desk
UK  0844 488 0999
US 888-502-6805
Email :   servic...@infinity-tracking.com
Mon - Fri 9am to 6pm UK, outside of our office hours our support team continuously monitors and maintains the Infinity Tracking platform.

_____ 

 Closing the loop 
 across all your marketing channels 
Reply all
Reply to author
Forward
0 new messages