Re: New Packager question again: can you point me to a not flawed package?
On Sat, May 31, 2008 at 9:59 PM, Russ Allbery <rra@debian.org> wrote:
> "Paul Johnson" <pauljohn32@gmail.com> writes:
>
>> I just need to see some examples of how this can be done. I wonder if
>> I'm running into a problem that is peculiar to Ubuntu. I can't find
>> packages that follow the principles we were discussing yesterday. In
>> fact, I can't find any that adhere to this guideline in a complete
>> way. (It appears to me the temptation is too great to make undocumented
>> changes in source code.)
>
> At this point, I've converted most of my packages to use Git, which means
> that the source package as uploaded to Debian has one collapsed patch
> including upstream changes and you have to check out the Git repository to
> see the separate branches and how they relate to upstream.
You don't keep a patches subdirectory under debian?
> At some point,
> I'm hoping to be able to generate format 3.0 packages from Git in some way
> that exposes the way that I'm actually working to other people working on
> packages.
I can't understand why you would do it this way. Seems like it would
lead to hard-to-catch coding mistakes. If there were 50 patches, some
of which others contribute, there might be a chance to figure which
one blows something up. As long as the patches are separate, there's
a chance I could back-track and find the problem. But it seems like
you are saying that you apply those 50 patches, and then make one
jumbo diff including all changes.
I thought--yesterday in this list--that people were telling me that is
a bad practice.. It destroys accountability.
>
> In the meantime, you can still look at the openafs package, which is
> currently using quilt and applies a whole bunch of patches (although we
> may switch to Git at some point down the road).
>
Cool, will look now! I like openafs and will probably re-package it
with customized server & cache settings for our lab.
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
Reply to: