From owner-freebsd-stable Tue Oct 13 13:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16951 for freebsd-stable-outgoing; Tue, 13 Oct 1998 13:27:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16943 for ; Tue, 13 Oct 1998 13:26:58 -0700 (PDT) (envelope-from djflow@erols.com) Received: from portbus1 (portbus1.tc.cc.va.us [164.106.211.24]) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id QAA09834 for ; Tue, 13 Oct 1998 16:22:28 -0400 (EDT) Message-ID: <000b01bdf6e7$f0b34280$18d36aa4@portbus1.tc.cc.va.us> From: "Derek Flowers" To: Subject: Tools for package indexing Date: Tue, 13 Oct 1998 16:27:43 -0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0007_01BDF6C6.67349A20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BDF6C6.67349A20 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0008_01BDF6C6.67349A20" ------=_NextPart_001_0008_01BDF6C6.67349A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable While in the process of working with the package files, I have created = some scripts to check and generate the index file needed by sysinstall = to work with packages. Hopefully, this will make someone's life a = little bit easier. I used them to split the package directory into two = separate entities so they will fit onto two CDs. Note that I am not a = top notch programmer. These scripts are quick and dirty, but they do = the job. By the way, is it possible for those who create the packages to include = the categories the package belongs to in the package file, perhaps as a = comment? The script that generates the index file grabs all the = information needed from the package file, but the only place I found to = get the categories is from the index file for the ports. It would be = much easier to get the categories from the package file itself. -Derek ------=_NextPart_001_0008_01BDF6C6.67349A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

While in the process of working with = the package=20 files, I have created some scripts to check and generate the index file = needed=20 by sysinstall to work with packages. Hopefully, this will make = someone's=20 life a little bit easier. I used them to split the package = directory into=20 two separate entities so they will fit onto two CDs. Note that I = am not a=20 top notch programmer. These scripts are quick and dirty, but they = do the=20 job.

By the way, is it possible for those = who create=20 the packages to include the categories the package belongs to in the = package=20 file, perhaps as a comment? The script that generates the index = file grabs=20 all the information needed from the package file, but the only place I = found to=20 get the categories is from the index file for the ports. It would = be much=20 easier to get the categories from the package file itself.

-Derek

------=_NextPart_001_0008_01BDF6C6.67349A20-- ------=_NextPart_000_0007_01BDF6C6.67349A20 Content-Type: application/x-compressed; name="pkgtools.tgz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pkgtools.tgz" H4sIAFS0IzYAA+2W70/aQBjHed2/4mvHgpqVtqiQxeH8MTAk80eMS1yGW2t7hYZyxVKmTvzfd9dr oYjTF1PckvvwguN693DP9+6eb51uz6cuuS68IKZh1DY2UADHuPcNVMxqFahWTaO2Zm7UDMA0DXOt AOMlF5UxGsZ2BBSiMIwfG3fVJSRYxIIWy5sl6Bc+1YddRTk9OG62PjfqVr8Xk/4Aetwf6EWjfJZg YTzGMnG6IdQv1L4ICOIQTkTsmLX4eM8PyJKKTZBrP4a5kgasPF9ARYze6xKHHdsOWoefGmflcllV FC+M0DzcOWjAp7A8dqixEwTQqN0nUFfLceeXCm0Q+TS2FDfErcKO3jGfULeSqEUxe4whcaERlIZ6 ebWt63ppto8FYn2Wwud3IjKAdgn1ezEJpYoVYQu6S37qdBQEyTjfwzcUP7IQlzBxzrviLqGKuAAi qaQpwoCGMbxwRF2VD/F8RbmDG1IyJ8DAdnp2hwxTDR7L+sHMtlBMd/2+go4dp8nk57XH5dUk+0TB exI0hQRZxL9Q4TYJdceX/6QWuyM/cHNawCUDwkoadW4Q+MNYSJOMnWRbSTs0lqh91YPWRHuM0i0S pbxl9e2wTdV3KL5f2cRdCR9SKSxs5WJwibIfOZVudOhtKo5NGHHdR9S/nP/zuV2crtyf7OjcnmRB /qUt2AuITXkik1ubLj/qT8/XtF1RXrvqSTL6L2//T/m/WamsZ/5fMdZrrMeortek/y+CvP8nxYFV MFHrzpWsMrCbm3Qp/Oaz1tnRSWu/rgrzDSO/oz7/q8Pi/XxS/1r8QvBqJsxYVDL2dG/ntLF/dPK1 LupwJgSLlhTg6TvAGH/wFO4otcRRxOvDoNf54VMv5MVbc6B52aLztpyti3lV+nbAPEjsR+5Re8w/ Dz7K20bDmkke24mdPxKxmGX9cPiZ2BMltllizMvUmf9KO8HFngbKjCTvFK99JyQSiUQikUgkEolE IpFIJBKJRCKRSCSS/5Xf2wImTQAoAAA= ------=_NextPart_000_0007_01BDF6C6.67349A20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message