| 1 |
Pete Gavin wrote: |
| 2 |
> |
| 3 |
> On Thu, Feb 22, 2001 at 06:03:52PM +0100, Achim Gottinger wrote: |
| 4 |
> > sys-build is no longer used instead the packages listed in |
| 5 |
> > current-packages.build are used together with the USE flags |
| 6 |
> > "build" and "build-static". |
| 7 |
> |
| 8 |
> Ok, I've removed the reference to sys-build. |
| 9 |
> |
| 10 |
> > |
| 11 |
> > I don't think it is neccesary to add -gentoo to our patches. |
| 12 |
> > Sometimes it is better to store patches without the ${PV} because |
| 13 |
> > the same patch can be used for different versions. |
| 14 |
> > Sometimes it is better to store patches in files/${PV} to keep the list |
| 15 |
> > in files small. |
| 16 |
> |
| 17 |
> Hmm... Yeah, I guess the -gentoo isn't entirely necessary, but in |
| 18 |
> certain cases, like when we update a kernel to a new version by using |
| 19 |
> a patch (which would simply be called something like linux-2.4.1.diff) |
| 20 |
> it *would* be necessary, and always using -gentoo would let others |
| 21 |
> know that the diff contains *our* modifications to the source tree, |
| 22 |
> instead of modifications we got somewhere else. |
| 23 |
|
| 24 |
An alternative whould be adding a header to our own patches, similar to |
| 25 |
the ones we use for the ebuilds, like glibc people do. |
| 26 |
Of cause your attempt is more transparent. |
| 27 |
|
| 28 |
And yes, if we have |
| 29 |
> alot of files that go with an ebuild, we should put them in |
| 30 |
> files/${PV}. I'll add that in to the howto. I think, though, that |
| 31 |
> patches should not be used between multiple versions of an ebuild, |
| 32 |
> because if they were, any changes/fixes that are made in the patch |
| 33 |
> would automatically be back-ported to previous versions of the |
| 34 |
> package. This totally defeats the purpose of having multiple revisions |
| 35 |
> of a package. |
| 36 |
> |
| 37 |
> > |
| 38 |
> > |
| 39 |
> > How about creating a new package in app-doc and place the Gentoo-HOWTO |
| 40 |
> > in there. |
| 41 |
> > |
| 42 |
> > I want to make a doc for the USE variables and this can be placed there |
| 43 |
> > too. |
| 44 |
> > |
| 45 |
> > Daniel, |
| 46 |
> > |
| 47 |
> > What do you think about using docbook for these docs. The sgml-tools |
| 48 |
> > should work quite well and we can produce the following output formates: |
| 49 |
> > dvi html man pdf ps rtf tex texi txt. |
| 50 |
> > We can add our own html-backend or an xml backend that can be used |
| 51 |
> > for xslt transformation. |
| 52 |
> > |
| 53 |
> |
| 54 |
> I know next to nothing about docbook/sgml/etc. Does anyone know a good |
| 55 |
> place to start learning about this? |
| 56 |
> |
| 57 |
|
| 58 |
http://www.oasis-open.org/docbook/documentation/reference/html/docbook.html |
| 59 |
|
| 60 |
achim~ |
| 61 |
> Pete |
| 62 |
> |
| 63 |
> _______________________________________________ |
| 64 |
> gentoo-dev mailing list |
| 65 |
> gentoo-dev@g.o |
| 66 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |
Archives