tech-pkg archive

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

Re: Reducing the number of patches in pkgsrc




To: "tech-pkg%NetBSD.org@localhost" <tech-pkg%NetBSD.org@localhost>

Subject: Re: Reducing the number of patches in pkgsrc

From: Aleksey Cheusov <cheusov%tut.by@localhost>

Date: Mon, 07 Jan 2008 19:47:08 +0200


> In other cases it is just the easiest way to make the package buildable
> with pkgsrc but is very hard to maintain in the long term because it cannot
> get integrated in the original source. In those cases, The Right Thing To
> Do (tm) would be to add some configurable option (eg,
> "--path-to-foo=/somewhere/pkgsrc/foo" for autoconf scripts) and submit
> _this_ patch to the software author.

A few weeks ago I've counted up a number of patches in autoconf-based
projects in pkgsrc. About 54% (!!!) of them contain patches either in
Makefile* or in configure* files.

Conclusion: The Right Thing To Do (TM) is to ask upstream maintainer
to NOT use autoshit at all ;-) Autoconf and automake are too hard to
most developers. They are overdesigned, are based upon bad idea etc.

-- 
Best regards, Aleksey Cheusov.



Follow-Ups:

Re: Reducing the number of patches in pkgsrc
From: Joerg Sonnenberger


References:

Reducing the number of patches in pkgsrc
From: Roland Illig

Re: Reducing the number of patches in pkgsrc
From: Greg Troxel

Re: Reducing the number of patches in pkgsrc
From: Klaus Heinz




Prev by Date: Re: patch filenames

Next by Date: Re: Reducing the number of patches in pkgsrc

Previous by Thread: Re: Reducing the number of patches in pkgsrc

Next by Thread: Re: Reducing the number of patches in pkgsrc

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index