Hello All!
I'd like to create my own pkg files. I've been using bsd for years,
but I've never bothered to learn how. Until now, I haven't needed to create them for my own software. But I find it slower to create the scripts than to create a package to install everything. I haven't
found any good tutorials, not even the older ones.
... A computer once beat me at chess, but it was no match for me at kickboxing.
--- CrashEdit 0.5.8 Linux
* Origin: Citrick BBS citlmbbs.synchro.net (86:534/20.1)
Hello Tanausu!
15 Jun 26 13:22, you wrote to all:
Hello All!
I'd like to create my own pkg files. I've been using bsd for years,
but I've never bothered to learn how. Until now, I haven't needed to
create them for my own software. But I find it slower to create the
scripts than to create a package to install everything. I haven't
found any good tutorials, not even the older ones.
Have you read the FreeBSD's Ports Development handbook?
https://docs.freebsd.org/en/books/porters-handbook/new-port/
Tanausu M. wrote to Javier Sturman <=-
Hi. I've searched so many websites that I'd forgotten to check the
freebsd handbook, thanks. I'll look at it carefully.
Tanausu M. wrote to Javier Sturman <=-
Hi. I've searched so many websites that I'd forgotten to check the
freebsd handbook, thanks. I'll look at it carefully.
Their discussion forums are also very helpful.
I'll be setting up a Dell Optiplex 390 box here with FreeBSD for MBSE development so if I run into anything, I'll pass it on.
One of my eventual goals is to move my BBS from Slackware Linux to FreeBSD.
I'll lose the DOS doors but it seems few callers use them anyway.
Their discussion forums are also very helpful.
I'll be setting up a Dell Optiplex 390 box here with FreeBSD for
MBSE development so if I run into anything, I'll pass it on.
One of my eventual goals is to move my BBS from Slackware Linux
to FreeBSD. I'll lose the DOS doors but it seems few callers use
them anyway.
If it's easier for you to maintain. I usually check it, or if I
receive forum updates by email.
I finally managed to do it calmly; it's nothing out of the ordinary, considering I'd never touched it before...
Hello Tanausu!
15 Jun 26 19:30, you wrote to Sean Dennis:
Their discussion forums are also very helpful.
I'll be setting up a Dell Optiplex 390 box here with FreeBSD for
MBSE development so if I run into anything, I'll pass it on.
One of my eventual goals is to move my BBS from Slackware Linux
to FreeBSD. I'll lose the DOS doors but it seems few callers use
them anyway.
If it's easier for you to maintain. I usually check it, or if I
receive forum updates by email.
I finally managed to do it calmly; it's nothing out of the ordinary,
considering I'd never touched it before...
I tried to port the latest Golded version (from @fidonet/golded) but I get way too many errors trying to build the proper Makefile. Didn't want flood the forum with my lack of development skills.
Javier
post-patch:
@${SED}\
-e 's,^\(#define __GVER_VENDOR_NAME__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_FIDO__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_EMAIL__\).*,\1 "${MAINTAINER}",'\
-e 's,\(#define __GVER_RELEASENAME__\).*,\1 "Golded+ FreeBSD port",'\
-e 's,\(#define __GVER_POSTVERSION__\).*,\1 "-b${SNAPDATE}",'\ <${WRKSRC}/golded3/mygolded.__h >${WRKSRC}/golded3/mygolded.h
I could take the existing Makefile and update it with GitHub, like I
did yesterday with mine. But I have no idea how to officially update
an existing port.
Some diff will have to be submitted.
... When everything is coming your way, you're in the wrong lane.
--- CrashEdit 0.5.8 Linux
* Origin: Citrick BBS citlmbbs.synchro.net (86:534/20.1)
Hello Tanausu!
16 Jun 26 00:32, you wrote to me:
post-patch:
@${SED}\
-e 's,^\(#define __GVER_VENDOR_NAME__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_FIDO__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_EMAIL__\).*,\1 "${MAINTAINER}",'\
-e 's,\(#define __GVER_RELEASENAME__\).*,\1 "Golded+ FreeBSD port",'\
-e 's,\(#define __GVER_POSTVERSION__\).*,\1 "-b${SNAPDATE}",'\
<${WRKSRC}/golded3/mygolded.__h >${WRKSRC}/golded3/mygolded.h
Which Golded version are you compiling?
I could take the existing Makefile and update it with GitHub, like I
did yesterday with mine. But I have no idea how to officially update
an existing port.
You should create a bug report in bugs.freebsd.org to that port and request to be a port maintainer, you can adopt an orphaned port.
More info on ports development.
https://docs.freebsd.org/en/books/porters-handbook/
Some diff will have to be submitted.
... When everything is coming your way, you're in the wrong lane.
--- CrashEdit 0.5.8 Linux
* Origin: Citrick BBS citlmbbs.synchro.net (86:534/20.1)
Javier
Hello Tanausu!
16 Jun 26 00:32, you wrote to me:
post-patch:
@${SED}\
-e 's,^\(#define __GVER_VENDOR_NAME__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_FIDO__\).*,\1 "",'\
-e 's,\(#define __GVER_VENDOR_EMAIL__\).*,\1 "${MAINTAINER}",'\
-e 's,\(#define __GVER_RELEASENAME__\).*,\1 "Golded+ FreeBSD port",'\
-e 's,\(#define __GVER_POSTVERSION__\).*,\1 "-b${SNAPDATE}",'\
<${WRKSRC}/golded3/mygolded.__h >${WRKSRC}/golded3/mygolded.h
Which Golded version are you compiling?
I could take the existing Makefile and update it with GitHub, like I
did yesterday with mine. But I have no idea how to officially update
an existing port.
You should create a bug report in bugs.freebsd.org to that port and request to be a port maintainer, you can adopt an orphaned port.
More info on ports development.
https://docs.freebsd.org/en/books/porters-handbook/
Some diff will have to be submitted.
... When everything is coming your way, you're in the wrong lane.
--- CrashEdit 0.5.8 Linux
* Origin: Citrick BBS citlmbbs.synchro.net (86:534/20.1)
Javier
| Sysop: | Kurisu |
|---|---|
| Location: | Memphis, TN |
| Users: | 8 |
| Nodes: | 32 (0 / 32) |
| Uptime: | 17:07:08 |
| Calls: | 55 |
| Files: | 73 |
| D/L today: |
15 files (7,839K bytes) |
| Messages: | 25,426 |
