<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04-08-14 18:03, Eduardo Machado
wrote:<br>
</div>
<blockquote
cite="mid:CAKXVDZfaMmVYxPLRcKSTR=G7uiy_pKzoVRVFYPQ9jKLe=2Gy=A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">
<div class="gmail_quote">
<div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> This actually makes sense to me. Most people will
only want one version<br>
> or the other of the lib, depending on what software
is using it. Having<br>
> it as a split package forces them to build both and
have all the deps<br>
> for both installed. Makes sense in a binary repo,
not so much in the<br>
> AUR.<br>
</blockquote>
<div><br>
</div>
</div>
<div>I thinked just liked this after i built these packages,
and therefore, i discovered that some of then aren' t</div>
<div>compatible with python2 and python3, two of then are
python2 only, so i had to comment some lines to</div>
<div>hide the python3 part. but i thought this was a bad
solution to only keep the script ready for python3
compatibility.</div>
<div class="im">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><br>
</div>
I just built the python-argparse split package in less
than three<br>
seconds. Build time isn't a valid argument here. Also, I
highly<br>
recommend building all AUR packages inside a chroot;
otherwise, you have<br>
no control of what happens on your file system (think of
broken build<br>
scripts that ignore $(DESTDIR) etc.)<br>
<br>
I think it is a good idea to use split packages unless
there are good<br>
reasons not to do so. Note that the AUR can also be
viewed as a staging<br>
area for source packages that might eventually be moved
to the official<br>
repositories. Not using split packages means more work
for Trusted Users<br>
and developers when moving.<br>
</blockquote>
</div>
</div>
<br>
</div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">Thinking
this way you are right.</div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px"><br>
</div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">Personally
i don't mind to work with one or another spec. But i would
like the advise of yours to standardize this "trade of". ;)</div>
</div>
</blockquote>
<br>
Nobody is forced to build everything in a split package.<br>
Aur packages are meant to be build with makepkg, and it's --pkg
option allows you to select which packages of a split package will
be build.<br>
<br>
If aur helpers don't support that functionality, register a bug
report with their maintainers.<br>
<br>
LVV<br>
</body>
</html>