Bug 483853 - Review Request: tcl-trf - Tcl extension providing "transformer" commands
Summary: Review Request: tcl-trf - Tcl extension providing "transformer" commands
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-03 22:29 UTC by Tom "spot" Callaway
Modified: 2009-03-16 19:51 UTC (History)
3 users (show)

Fixed In Version: 2.1.3-2.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-16 19:42:54 UTC
Type: ---
Embargoed:
mmaslano: fedora-review+
tcallawa: fedora-cvs+


Attachments (Terms of Use)

Description Tom "spot" Callaway 2009-02-03 22:29:01 UTC
Spec URL: http://www.auroralinux.org/people/spot/review/new/tcl-trf.spec
SRPM URL: http://www.auroralinux.org/people/spot/review/new/tcl-trf-2.1.3-1.fc11.src.rpm
Description: 
Trf is an extension library to the script language tcl. It provides
transformer procedures which change the flow of bytes through a channel
in arbitrary ways. The underlying functionality in the core is that of
stacked channels which allows code outside of the core to intercept all
actions (read/write) on a channel.

Among the applications of the above provided here are compression,
charset recording, error correction, and hash generation.

Comment 1 Vinagre 2009-02-19 11:49:02 UTC
Thanks,
Hope this will be added soon, I need this library.

Comment 2 Marcela Mašláňová 2009-03-06 15:25:41 UTC
OK Rpmlint must be run on every package.
OK The package must be named according to the Package Naming Guidelines.
OK The spec file name must match the base package %{name}.
OK The package must meet the Packaging Guidelines.
OK The package must be licensed with a Fedora approved license.
? The License field in the package spec file must match the actual license.
OK If (and only if) the source package includes the text of the license(s) in its own file.
OK The spec file must be written in American English.
OK The spec file for the package MUST be legible.
OK The sources used to build the package must match the upstream source. 113c9766640239b17ee2dad4d3af4757
OK The package MUST successfully compile.
OK Correct BuildRequires.
OK Proper use of %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
OK Shared library files (not just symlinks) must call ldconfig in %post and %postun.
OK Relocatable package must state this fact in the request for review.
OK A package must own all directories that it creates.
OK A package must not contain any duplicate files in the %files listing.
OK Permissions on files must be set properly.
OK Each package must have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).
OK Each package must consistently use macros.
OK The package must contain code, or permissable content.
OK Large documentation files must go in a -doc subpackage.
OK If a package includes something as %doc, it must not affect the runtime of the application.
OK Header files must be in a -devel package.
OK Static libraries must be in a -static package.
OK Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig'.
OK Library files with a suffix (e.g. libfoo.so.1.1) and files that end in .so (without suffix) must go in -devel.
OK In the vast majority of cases, devel packages must require the base package.
OK Packages must NOT contain any .la libtool archives.
OK Packages containing GUI applications must include a %{name}.desktop file.
OK At the beginning of %install, each package MUST run rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

Licenses: Hybrid BSD (half BSD, half zlib) in bzlib.h, sha.h is openssl license? generic/haval hasn't license at all...
Could you check it once more and set the appropriate one? I didn't find any license file, what upstream says about license?

Comment 3 Tom "spot" Callaway 2009-03-11 15:10:51 UTC
Well, I got all of the licensing cleared up on this one except for the RipeMD stuff, that's all non-free, so I need to pull that code out. :/

Comment 4 Tom "spot" Callaway 2009-03-12 16:23:15 UTC
Okay, I'm pretty sure I have it all settled now:

New SRPM: http://auroralinux.org/people/spot/review/new/tcl-trf-2.1.3-2.fc11.src.rpm
New SPEC: http://auroralinux.org/people/spot/review/new/tcl-trf.spec

Comment 5 Marcela Mašláňová 2009-03-13 11:55:28 UTC
You've probably got all of them. I'm sorry but I'm still unsure about those files:
trf2.1.3/compat/stdlib.h
trf2.1.3/compat/tcl*.c
They are speaking about some license.terms, which are not there. Could be tcl* files under tcl license?

Comment 6 Tom "spot" Callaway 2009-03-13 13:28:56 UTC
They are files from TCL, thus, under the TCL license. However, they're not used on Linux (we have stdlib.h so we never include compat/stdlib.h, and the compat/tcl* code is only used on windows or cross-compile environments).

Comment 7 Marcela Mašláňová 2009-03-13 13:39:44 UTC
Ok, ACCEPT

Comment 8 Tom "spot" Callaway 2009-03-13 14:01:09 UTC
New Package CVS Request
=======================
Package Name: tcl-trf
Short Description: Tcl extension providing transformer commands
Owners: spot
Branches: F-9 F-10 devel
InitialCC: 

... and it's done.

Comment 9 Fedora Update System 2009-03-13 14:54:29 UTC
tcl-trf-2.1.3-2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/tcl-trf-2.1.3-2.fc9

Comment 10 Fedora Update System 2009-03-13 14:54:35 UTC
tcl-trf-2.1.3-2.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/tcl-trf-2.1.3-2.fc10

Comment 11 Fedora Update System 2009-03-16 19:42:49 UTC
tcl-trf-2.1.3-2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2009-03-16 19:51:53 UTC
tcl-trf-2.1.3-2.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.