Prev: Cheap wholesale 2010 World Cup jerseys by paypal and free shipping
Next: Question about CDPATH in bash...
From: John Kelly on 13 Jun 2010 08:08

With some software, like apache and a few others, I don't use a distro
package, I get the upstream tarball and hack the code to make my own
local patches, to better integrate it with my environment. I may also
use some distro patches, if they seem applicable to my needs.

Organizing, maintaining, and merging the patches can get tedious, and I
wanted a tool to make it less of a chore. So I wrote a bash script for
that purpose. I call it ha, the hack artisan. It's available here:

ftp://ftp.beewyz.com/users/jar/etcetera/computer/programming/project/ha/

It does not handle file names with embedded blanks, and it only handles
tar.gz tarballs. You can make improvements yourself, so try not to
complain. It's also bash specific, it's not intended to be portable to
other shells.

If you see other bugs though, maybe I can fix them.


--
Web mail, POP3, and SMTP
http://www.beewyz.com/freeaccounts.php

From: John Kelly on 13 Jun 2010 08:41
On Sun, 13 Jun 2010 12:08:48 +0000, John Kelly <jak(a)isp2dial.com> wrote:

>I call it ha, the hack artisan. It's available here:

>ftp://ftp.beewyz.com/users/jar/etcetera/computer/programming/project/ha/

And lest you ask "why not just use a repo manager like git?"

I don't need a repo manager. I'm not contributing patches back to the
project, they're just local hacks not useful to anyone else.

With my approach, patches stay in their own directory tree, and don't
get lost in a big repo forest. When collecting patches from multiple
distro suppliers, that makes it easier to track and maintain them.

The hack artisan is a lightweight solution to the problem. Use a repo
manager if you prefer.


--
Web mail, POP3, and SMTP
http://www.beewyz.com/freeaccounts.php

From: Thomas 'PointedEars' Lahn on 13 Jun 2010 18:02
John Kelly wrote:

> With some software, like apache and a few others, I don't use a distro
> package, I get the upstream tarball and hack the code to make my own
> local patches, to better integrate it with my environment.

I do not think that is a wise course of action. Proper package management
leaves your configuration files untouched on updated unless you want it
differently, so there is hardly a need to patch software manually in order
to fit it to one's environment. Short of the kernel, of course, but then
patch(1) suffices. From linux/README:

gzip -cd ../patch-2.6.xx.gz | patch -p1

> I may also use some distro patches, if they seem applicable to my needs.
>
> Organizing, maintaining, and merging the patches can get tedious, and I
> wanted a tool to make it less of a chore. So I wrote a bash script for
> that purpose. I call it ha, the hack artisan. It's available here:
>
> ftp://ftp.beewyz.com/users/jar/etcetera/computer/programming/project/ha/
>
> It does not handle file names with embedded blanks,

It could if you used double-quotes consistently, like

cp -aT ".temp/.revise/$this" $version

instead of

cp -aT .temp/.revise/$this $version

Still, this is the path to the Dark Side.

> and it only handles tar.gz tarballs. You can make improvements yourself,
> so try not to complain.

Rest assured I won't. I'll stick to proper package management and patch(1)
instead.

> It's also bash specific, it's not intended to be portable to other shells.

So a bit off-topic here in comp.*unix*.shell, isn't it?

> If you see other bugs though, maybe I can fix them.

I don't think I care much for finding out what it does (it is completely
undocumented), or fix bugs in an approach that I think is flawed from the
outset. Sorry.


PointedEars
From: pk on 13 Jun 2010 17:53
Thomas 'PointedEars' Lahn wrote:

>> If you see other bugs though, maybe I can fix them.
>
> I don't think I care much for finding out what it does (it is completely
> undocumented), or fix bugs in an approach that I think is flawed from the
> outset. Sorry.

Thanks for letting everyone know.
From: Kenny McCormack on 13 Jun 2010 19:33
In article <2018127.hmKxfEcJ0L(a)xkzjympik>, pk <pk(a)pk.invalid> wrote:
>Thomas 'PointedEars' Lahn wrote:
>
>>> If you see other bugs though, maybe I can fix them.
>>
>> I don't think I care much for finding out what it does (it is completely
>> undocumented), or fix bugs in an approach that I think is flawed from the
>> outset. Sorry.
>
>Thanks for letting everyone know.

Yeah, I was definitely on the edge of my chair waiting for the
PointedEars verdict.

--
> No, I haven't, that's why I'm asking questions. If you won't help me,
> why don't you just go find your lost manhood elsewhere.

CLC in a nutshell.

 |  Next  |  Last
Pages: 1 2 3
Prev: Cheap wholesale 2010 World Cup jerseys by paypal and free shipping
Next: Question about CDPATH in bash...