Mailing List Archive

On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> Hello,
>
> Attached is the file I used for SUSE and the python-policyd-spf
>
Boyd,

It looks to me like that may be from SVN and not from the release tarball.
There are files at the SVN trunk that aren't in the release tarball because
they aren't needed/haven't been made to work yet. Please double check you
just got the tarball from http://www.openspf.org/Software.

Scott K

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

On Fri, 2 Mar 2007, Scott Kitterman wrote:
> On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> > Hello,
> >
> > Attached is the file I used for SUSE and the python-policyd-spf
> >
> Boyd,
>
> It looks to me like that may be from SVN and not from the release tarball.
> There are files at the SVN trunk that aren't in the release tarball because
> they aren't needed/haven't been made to work yet. Please double check you
> just got the tarball from http://www.openspf.org/Software.

I got the files from 0.2 as they were not in 0.3. They were needed for
the rpm.

--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> Hello,
>
> Attached is the file I used for SUSE and the python-policyd-spf
>
I just got a chance to take a look at the spec file for this. That locations
that your spec file will install the file is different than that called out
in the upstream provided documenation. I recommend that you look at the
INSTALL.Debian file and provide a opensuse equivalent that provides the
correct path to the executable for your distribution. I'd also change the
detailed description to refer to your opensuse specific documentation rather
than the Debian specific documentation

Also, I didn't see in the spec file where the man page gets installed, not
sure if something specific is needed for that or not.

Scott K

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

On Fri, 2 Mar 2007, Scott Kitterman wrote:
> On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> > Hello,
> >
> > Attached is the file I used for SUSE and the python-policyd-spf
> >
> I just got a chance to take a look at the spec file for this. That locations
> that your spec file will install the file is different than that called out
> in the upstream provided documenation. I recommend that you look at the
> INSTALL.Debian file and provide a opensuse equivalent that provides the
> correct path to the executable for your distribution. I'd also change the
> detailed description to refer to your opensuse specific documentation rather
> than the Debian specific documentation
>
> Also, I didn't see in the spec file where the man page gets installed, not
> sure if something specific is needed for that or not.

Here is a beginning. Why do you exclude the files needed from the trunk
to the distribution? I really think the files should be included. They
were in .2 but not in .3

Thanks,

--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

On Saturday 03 March 2007 00:56, Boyd Lynn Gerber wrote:
> On Fri, 2 Mar 2007, Scott Kitterman wrote:
> > On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> > > Hello,
> > >
> > > Attached is the file I used for SUSE and the python-policyd-spf
> >
> > I just got a chance to take a look at the spec file for this. That
> > locations that your spec file will install the file is different than
> > that called out in the upstream provided documenation. I recommend that
> > you look at the INSTALL.Debian file and provide a opensuse equivalent
> > that provides the correct path to the executable for your distribution.
> > I'd also change the detailed description to refer to your opensuse
> > specific documentation rather than the Debian specific documentation
> >
> > Also, I didn't see in the spec file where the man page gets installed,
> > not sure if something specific is needed for that or not.
>
> Here is a beginning. Why do you exclude the files needed from the trunk
> to the distribution? I really think the files should be included. They
> were in .2 but not in .3
>
From what little I know about spec files, I don't find any problems.

Tumgreyspf, which is the project I derived this from, has a complete spec file
in their source. I took a stab at updating it for this derivative, but don't
know enough to know if what I did was complete or correct. My intent is to
only provide files for the tagged releases that are complete/correct/needed.

I've added your spec file (not updated yet, but I will) to the SVN trunk and
will keep it up to date with whatever changes you provide. That way when I
release the next version, the spec file will be there and this will be
easier.

I'm all for putting the packaging information into the tagged releases when I
know it to be correct. I answer to your why question, I think for 0.2 I
copied all the files to the tag and then only included what I saw as the
useful files in the tarball. For 0.3 I think I decided there was little
point in that and I should limit the tagged branch to what I knew to be
correct and needed. The next release will have your spec file and (let me
know which they are) any other of the files that you needed.

Scott K

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007