[Bug 245597] Review Request: pygtksourceview - Python bindings for gtksourceview

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: pygtksourceview - Python bindings for gtksourceview


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245597


toshio@xxxxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |toshio@xxxxxxxxxxxxxxx




------- Additional Comments From toshio@xxxxxxxxxxxxxxx  2007-06-27 18:20 EST -------
(In reply to comment #9)
> No, please. 
> 
> The package was in before, there is a merge review ticket for it too.
> Don't make me just through more hoops than necessary. I'll take care of
> resolving any conflicts before building the package.

I realize that it may seem like hoop jumping to have to put through review a
package which was already in the distribution.  And if that was the case, then
it definitely would be.  Unfortunately, a compat-* package is a new package with
new requirements.  As you note, there can be conflicts that arise from such a
package that need to be resolved before building and pushing it into the
repository with the non-compat version.  Resolving the immediate source of
filesystem conflicts can sometimes require patching source to look in different
directories as well.  With C libraries, header files and other development bits
may be pruned out.  A compat-* package is a different beast from the normal
package that spawns it.

You're an experienced enough packager that your first stab at a package will
probably be excellent.  You have an excellent reviewer in tibbs lined up and
ready to review it.  So there won't be much holdup between the time you submit
and the time it hits the repository.  That may tempt you into thinking a
compat-* package is trivial and the review mere bureaucracy.  But think for a
moment of what happens when we have other, less experienced packagers,
submitting compat-* packages.   Experience with compat-* packages in Extras has
shown that even moderately experienced packagers tend to forget some things when
packaging compat-* packages for the simple reason that they have special caveats
that are different from the non-compat packages those packagers are used to
creating.  We need the review step to help catch these problems.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]