Writing a Package Manager

Re:Writing a Package Manager by david2ndaccount on Wednesday August 23, 2023 @02:06AM (#37232360)

Honestly pretty strange to write a package manager for sqlite and to use directories + json files to store the data instead of sqlite.

[ Parent | on HN ]

Re:Writing a Package Manager by gosenx on Wednesday August 23, 2023 @02:56AM (#37232671)

Great point

[ Parent | on HN ]

Re:Writing a Package Manager by gjvc on Wednesday August 23, 2023 @04:39AM (#37233332)

[delayed]

[ Parent | on HN ]

Re:Writing a Package Manager by grumblingdev on Wednesday August 23, 2023 @07:26AM (#37234266)

SQL not so good for tree structures. Recursive CTEs are pretty gnarly.

Graphdb would be ideal.

[ Parent | on HN ]

Re:Writing a Package Manager by jeremyjh on Wednesday August 23, 2023 @08:14AM (#37234678)

You want to bring in a dependency to avoid writing one 8 line CTE?

[ Parent | on HN ]

Re:Writing a Package Manager by christophberger on Wednesday August 23, 2023 @09:47AM (#37235782)

The number of lines needed is not a good measure for gnarliness.

(To be fair, I don't know if gnarliness is measurable at all.)

[ Parent | on HN ]

Re:Writing a Package Manager by jeremyjh on Wednesday August 23, 2023 @12:09PM (#37238216)

It isn’t gnarly at all, but recursive CTE are outside the experience of most SQL devs. Here “gnarly” is used to describe “unfamiliar”.

[ Parent | on HN ]

Re:Writing a Package Manager by jbverschoor on Wednesday August 23, 2023 @10:27AM (#37236498)

SQLite is a pretty darn good solution for any file(set) that needs atomic / consistent writes

[ Parent | on HN ]

Re:Writing a Package Manager by edgyquant on Wednesday August 23, 2023 @11:38AM (#37237738)

Why not? Just add child/parent ids

[ Parent | on HN ]

Re:Writing a Package Manager by nalgeon on Wednesday August 23, 2023 @10:41AM (#37236759)

A couple of reasons:

1) I wanted human readable specs and lockfiles.

2) I didn't want to introduce a dependency.

[ Parent | on HN ]