On Nov 8, 2007 1:08 PM, Aaron Griffin wrote:

On Nov 8, 2007 1:03 PM, Jonathan wrote:

...

I haven't been able to find any arch documentation (besides the mailing lists) on the splitting of base into base and base-devel groups. The main need is for people to understand the need to install the base-devel group before building packages. the makepkg man page seems like a good place for this.

That's probably a good idea - would you be willing to write it up? It's documentation so I'm sure you could probably just propose a paragraph here and I can copy-pasta it into the man page.

Documentation in the manpages shouldn't be Arch Linux specific. -Dan

Aaron Griffin wrote:

On Nov 8, 2007 1:10 PM, Dan McGee wrote: [snip]

...

Documentation in the manpages shouldn't be Arch Linux specific.

Good catch, this is why we pay you the big bucks.

Well, shouldn't the man page for makepkg be Arch Specific?

Dan McGee wrote:

On Nov 8, 2007 4:42 PM, R. Dale Thomas wrote:

...

Aaron Griffin wrote:

...

On Nov 8, 2007 1:10 PM, Dan McGee wrote: [snip]

...

Documentation in the manpages shouldn't be Arch Linux specific. Good catch, this is why we pay you the big bucks.

Well, shouldn't the man page for makepkg be Arch Specific?

Care to explain your logic? I know *for a fact* that we aren't the only people using makepkg.

-Dan

Ok, Dan, I'll try. Makepkg is from a package produced by Arch and its developers. The man page _should_ accurately depict the usage of that program as it pertains to Arch. Makepkg is not a generic package and its man page would not be included in generic man-pages on other distro's but should be included (when man-pages are included) for Arch. Perhaps that is not 'technically' Arch specific, but it seemed to me to be so.

Aaron Griffin wrote:

On Nov 8, 2007 5:27 PM, R. Dale Thomas wrote:

...

Makepkg is not a generic package and its man page would not be included in generic man-pages on other distro's

That's actually false. As Dan said, ArchLinux users are not the only ones using makepkg.

I understood that, yes.

Even if this weren't the case - makepkg is INTENDED to be used elsewhere. makepkg and pacman are brothers. It's hard to use pacman without makepkg and hard to use makepkg with pacman.

And this too. Sorry, guys, I certainly was _not_ trying to be difficult, here. I must have gotten totally confused about the train of thought on this topic. I concede all points to Dan & Aaron.

2007/11/8, Dan McGee :

On Nov 8, 2007 1:08 PM, Aaron Griffin wrote:

...

On Nov 8, 2007 1:03 PM, Jonathan wrote:

...

I haven't been able to find any arch documentation (besides the mailing lists) on the splitting of base into base and base-devel groups. The main need is for people to understand the need to install the base-devel group before building packages. the makepkg man page seems like a good place for this.

That's probably a good idea - would you be willing to write it up? It's documentation so I'm sure you could probably just propose a paragraph here and I can copy-pasta it into the man page.

Documentation in the manpages shouldn't be Arch Linux specific.

It could be documented in our official Install Guide in Pacman section. -- Roman Kyrylych (Роман Кирилич)

On Nov 9, 2007 5:02 AM, bardo wrote:

2007/11/8, Dan McGee :

...

Documentation in the manpages shouldn't be Arch Linux specific.

So, what about patching it to be arch-specific when its package is built? This way you can distribute a source package that contains the general man-page, while you can get an extra "ARCH BEHAVIOR" section that's going to show up only when using the arch PKGBUILD.

That's the farthest thing from elegant I've heard in this thread. Why is this such a big deal? I really don't get it. Document it on the wiki if this is a problem for you.