Bug 65631

Summary:	patch eclass
Product:	Gentoo Linux	Reporter:	Dmitry S. Kulyabov <yamadharma>
Component:	New packages	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	dragonheart, powerman-asdf, yamadharma
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	eclass/patch.eclass

Description Dmitry S. Kulyabov 2004-09-27 22:29:51 UTC

Patches arrangement

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Dmitry S. Kulyabov 2004-09-27 22:31:16 UTC

Created attachment 40579 [details]
eclass/patch.eclass

Comment 2 Daniel Black (RETIRED) gentoo-dev

2004-09-28 02:01:37 UTC

Please explain the purpose of this eclass modification.

Please also attach the differance between this file and the original as a text patch attachment.

Comment 3 Seemant Kulleen (RETIRED) gentoo-dev

2004-09-29 09:22:46 UTC

dimitry please see previous comment

Comment 4 SpanKY gentoo-dev

2004-09-29 11:38:21 UTC

most of this is handled by epatch in eutils.eclass while the rest i dont think needs an eclass to handle

Comment 5 Dmitry S. Kulyabov 2004-09-30 00:10:39 UTC

This isn't simple function like epatch().
This may be like UNIPATCH conception from kernel-2.ebuild.
This eclass for uniform placement and automatic applaying patches.

Comment 6 SpanKY gentoo-dev

2004-09-30 08:21:36 UTC

epatch isnt just a 'simple' function

it can be used for bulk patching ... i dont really see a need for automatic patching such as you describe; people can use epatch

if the only thing that would benefit here is the kernel, they already have their own patch system in place

in other words, this eclass needs to have a justification before it will be added