Hi, I'm maintaining ipython in [community]. Right now, the PKGBUILD just removes all the docs. I can see the reasoning. The compressed package size grows nearly five-fold when they are included. I have several options. I can keep on stripping docs, I can include the docs in the ipython package, or I can generate a split package. I wrote a PKGBUILD that produces the split packages ipython and ipython-doc. I noticed that koffice from [extra] has its docs split. But nobody seems to be doing that for anything in [community]. So should I go ahead and commit my split PKGBUILD?
-- Chris
On Monday 08 March 2010 23:29:09 Chris Brannon wrote:
Hi, I'm maintaining ipython in [community]. Right now, the PKGBUILD just removes all the docs. I can see the reasoning. The compressed package size grows nearly five-fold when they are included. I have several options. I can keep on stripping docs, I can include the docs in the ipython package, or I can generate a split package. I wrote a PKGBUILD that produces the split packages ipython and ipython-doc. I noticed that koffice from [extra] has its docs split. But nobody seems to be doing that for anything in [community]. So should I go ahead and commit my split PKGBUILD?
-- Chris
IMHO you should split it. Also, what prefix docs packages should have? Because I see more -docs and a lot of -doc (mainly texlive packages) in our repo.
On 09/03/10 08:40, Andrea Scarpino wrote:
On Monday 08 March 2010 23:29:09 Chris Brannon wrote:
Hi, I'm maintaining ipython in [community]. Right now, the PKGBUILD just removes all the docs. I can see the reasoning. The compressed package size grows nearly five-fold when they are included. I have several options. I can keep on stripping docs, I can include the docs in the ipython package, or I can generate a split package. I wrote a PKGBUILD that produces the split packages ipython and ipython-doc. I noticed that koffice from [extra] has its docs split. But nobody seems to be doing that for anything in [community]. So should I go ahead and commit my split PKGBUILD?
-- Chris
IMHO you should split it.
Agreed. namcap from [testing] should give you a warning about too many docs if you left it in one package.
Also, what prefix docs packages should have? Because I see more -docs and a lot of -doc (mainly texlive packages) in our repo.
docs? Not that it matters...
On Tue 09 Mar 2010 10:25 +1000, Allan McRae wrote:
On 09/03/10 08:40, Andrea Scarpino wrote:
On Monday 08 March 2010 23:29:09 Chris Brannon wrote:
Hi, I'm maintaining ipython in [community]. Right now, the PKGBUILD just removes all the docs. I can see the reasoning. The compressed package size grows nearly five-fold when they are included. I have several options. I can keep on stripping docs, I can include the docs in the ipython package, or I can generate a split package. I wrote a PKGBUILD that produces the split packages ipython and ipython-doc. I noticed that koffice from [extra] has its docs split. But nobody seems to be doing that for anything in [community]. So should I go ahead and commit my split PKGBUILD?
-- Chris
IMHO you should split it.
Agreed. namcap from [testing] should give you a warning about too many docs if you left it in one package.
Also, what prefix docs packages should have? Because I see more -docs and a lot of -doc (mainly texlive packages) in our repo.
docs? Not that it matters...
doc would be short for documentation docs would be short for docsumentation?
Loui Chang wrote:
On Tue 09 Mar 2010 10:25 +1000, Allan McRae wrote:
*SNIP*
docs? Not that it matters...
doc would be short for documentation docs would be short for docsumentation?
In speech or email, people regularly use phrases like "read the docs". I have no idea why. It's just colloquial, I guess. A friend of mine abbreviates documentation as docu.
-- Chris
On 09/03/10 11:07, Loui Chang wrote:
On Tue 09 Mar 2010 10:25 +1000, Allan McRae wrote:
On 09/03/10 08:40, Andrea Scarpino wrote:
On Monday 08 March 2010 23:29:09 Chris Brannon wrote:
Hi, I'm maintaining ipython in [community]. Right now, the PKGBUILD just removes all the docs. I can see the reasoning. The compressed package size grows nearly five-fold when they are included. I have several options. I can keep on stripping docs, I can include the docs in the ipython package, or I can generate a split package. I wrote a PKGBUILD that produces the split packages ipython and ipython-doc. I noticed that koffice from [extra] has its docs split. But nobody seems to be doing that for anything in [community]. So should I go ahead and commit my split PKGBUILD?
-- Chris
IMHO you should split it.
Agreed. namcap from [testing] should give you a warning about too many docs if you left it in one package.
Also, what prefix docs packages should have? Because I see more -docs and a lot of -doc (mainly texlive packages) in our repo.
docs? Not that it matters...
doc would be short for documentation docs would be short for docsumentation?
documents?
Allan McRae wrote:
On 09/03/10 08:40, Andrea Scarpino wrote:
*SNIP*
IMHO you should split it.
Agreed. namcap from [testing] should give you a warning about too many docs if you left it in one package.
Great! I just wanted to make sure that I'm on the right track. Thanks for the replies.
Also, what prefix docs packages should have? Because I see more -docs and a
lot
of -doc (mainly texlive packages) in our repo.
docs? Not that it matters...
I have -docs in my PKGBUILD now, and I'll stick with that.
-- Chris
aur-general@lists.archlinux.org